HYPER SANDBOXISOLATED · ZX CORE
Our own lightweight hypervisor rapidly observes behavior across multiple OS and app versions.
With no agent inside the VM, it resists evasion such as sandbox detection and sleep-based bypasses.
The Hyper Sandbox runs the document to extract events and behaviors, then chains the behaviors and matches them against attack sequences.
In this sample, the shell → remote download → executable creation → execution sequence matched, and the AI judged it Risk 10 · malicious.
File name, events, scores, techniques and URL: example values from a sample analysis report (analysis flow)
Analysis, disarm and blocking, plus deployment and operations features, are layered around the Hyper Sandbox at the center.
The MTA · ICAP · REST API band at the bottom connects to your existing equipment and security operations.
Legacy sandboxes get stuck on speed, evasion, environment fidelity and infrastructure cost.
Here's how the ZX Hyper Sandbox overcomes each limit, side by side.
When mail and files pile up, bottlenecks mean only some get inspected.
Malware spots the analysis through VM detection, demands for user interaction and delayed execution, then hides.
Not every OS and app version on company PCs can be reproduced in a virtual environment.
Requires OS and Office licenses for analysis and high-performance servers with about 5 GB per sandbox.
Lightweight hypervisor analysis · forced execution of threat elements · adaptive analysis environment.
Together they expose malicious behavior that hides or waits for a click.
Detection case · We ran a hidden hyperlink in an HWP document from APT37's ‘Artemis’ campaign and caught concealed PowerShell activity.
This technology was selected as a 2025 KISA excellent information security technology.