Which versions of ventra-kit are malicious?

The following npm versions of ventra-kit are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate ventra-kit if I installed it?

ventra-kit 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 ventra-kit — how do I know if it already compromised me?

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

Yes — ventra-kit is associated with the IN-MAL-2026-017659 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 ventra-kit 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 ventra-kit (version 1.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ventra-kit across your stack and pipelines.

Malicious package

ventra-kitnpm

ventra-kit is a confirmed malicious npm package (MAL-2026-13962) that steals credentials and exfiltrates sensitive data (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ventra-kit (npm)

MAL-2026-13962

Immediate action

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

npm uninstall ventra-kit

What this malware does

The package's default export (module.exports = () => getPlugin()) issues an HTTPS request to a hardcoded bare-IP host at 31.97.137.157:45000/icons/116 and passes the response's credits field into new Function('require','module','exports',...,'Promise', data.credits), executing attacker-controlled JavaScript with full Node.js capabilities (require, process, Buffer, globals). The destination URL is assembled from split protocol/separator/domain/path constants, and an unused iconDomain map (cloudflare/fastly/akamai) plus a setDefaultModule helper referencing cdnjs/font-awesome provide cover-story framing that disguises the loader as an icon CDN helper. Declared dependencies (@primno/dpapi, better-sqlite3, node-machine-id) are consistent with a Windows browser-credential stealer to be delivered as the remote payload. Any consumer that requires ventra-kit and invokes the default export receives remote code execution on the installer's machine.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

3f023d55f53d30a92c8f06ca661862ee99d338f6d3719247c9390b3169009702

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 ventra-kit (version 1.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ventra-kit across your stack and pipelines.
If you installed it — respond
ventra-kit 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 ventra-kit 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 ventra-kit 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. ventra-kit on npm has been identified as a malicious package (version 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017659

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ventra-kit-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