Which versions of vantora are malicious?

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

How do I remediate vantora if I installed it?

vantora is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

If vantora 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 vantora part of a known attack campaign?

Yes — vantora is associated with the GHSA-4fm5-fwqx-8r39, IN-MAL-2026-013201, IN-MAL-2026-013200 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 vantora 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 vantora (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vantora across your stack and pipelines.

Malicious package

vantoranpm

vantora is a confirmed malicious npm package (MAL-2026-11016) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vantora (npm)

MAL-2026-11016

Immediate action

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

npm uninstall vantora

What this malware does

The package [email protected] (6 files) exhibits no observable supply-chain attack behavior. There are no lifecycle scripts fetching or executing remote content, no reads of installer secret paths (~/.aws, ~/.ssh, ~/.npmrc, browser profile stores), no hardcoded exfiltration endpoints, no obfuscated payloads, no credential distribution, and no backdoor or self-propagation mechanics. No evidence of an installer-side attacker benefit or install/import-time destructive action is present.

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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

530a2162909707ce34212e910d9a625ad0a4a6a746a7a48f5e3f3523b3b3df23

0ae71b2f5b28b01c4c66ffdebb779fe733c946c76d66eece4da8d73a78a3cca9

6b247c0aaff056911572cd72fb377332194aa11aa4ada038039e3c35a6755e2a

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vantora (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vantora across your stack and pipelines.
If you installed it — respond
vantora is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If vantora 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 vantora 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. vantora on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4fm5-fwqx-8r39IN-MAL-2026-013201IN-MAL-2026-013200

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks vantora-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database