Which versions of vor8zakon are malicious?

The following npm versions of vor8zakon are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate vor8zakon if I installed it?

vor8zakon carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.

I already installed vor8zakon — how do I know if it already compromised me?

If vor8zakon was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is vor8zakon part of a known attack campaign?

Yes — vor8zakon is associated with the GHSA-9f89-97fj-pqmp, IN-MAL-2026-010789 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find vor8zakon across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vor8zakon (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vor8zakon across your stack and pipelines.

Malicious package

vor8zakonnpm

vor8zakon is a confirmed malicious npm package (MAL-2026-10694) that runs destructive / sabotage code (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vor8zakon (npm)

MAL-2026-10694

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall vor8zakon

What this malware does

Package advertises itself as 'A simple cryptographic library for JavaScript applications' but ships no crypto code and exports nothing. package.json declares a postinstall hook (node index.js) that detects the host OS and runs platform-specific commands: on Windows it builds a UTF16LE+base64 PowerShell EncodedCommand and runs it via powershell -WindowStyle Hidden -EncodedCommand <blob>; on macOS it invokes osascript; on Linux it spawns python3 -c "import os; os.system('gnome-calculator &')". After execution, a cleanUp() routine renames a sibling package.md over package.json (replacing the manifest with a decoy) and deletes index.js itself, leaving a victim auditing the installed package directory with an innocuous manifest and no payload file. The current GUI-calculator action is a placeholder, but the harness — purpose mismatch, hidden-window obfuscated PowerShell, multi-platform install-time exec, manifest swap, self-deletion, empty README, throwaway author — is a working install-time RCE delivery channel and an anti-forensic dropper pattern, not a crypto library.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

721d7e16a5301a1aa9df428ffbe01436fa3d36f2700a8b2d62dd40ed8b743034

99924288481504c324c3f573ba7ba99ac4e1c7a7f22a940c94d81059b868fdfd

Detection & response playbook

Destructive / sabotage

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vor8zakon (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vor8zakon across your stack and pipelines.
If you installed it — respond
vor8zakon carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.
Did it already run?
If vor8zakon was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks vor8zakon before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. vor8zakon on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9f89-97fj-pqmpIN-MAL-2026-010789

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks vor8zakon-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database