Which versions of ventrix-kit are malicious?

The following npm versions of ventrix-kit are flagged malicious: 0.5.2, 1.5.2. Treat any of these as compromised.

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

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

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

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

Malicious package

ventrix-kitnpm

ventrix-kit is a confirmed malicious npm package (MAL-2026-12494) that steals credentials and exfiltrates sensitive data (malicious versions 0.5.2, 1.5.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ventrix-kit (npm)

MAL-2026-12494

Immediate action

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

npm uninstall ventrix-kit

What this malware does

[email protected] ships a loader that, when the package's default getPlugin export is invoked, performs an HTTP request to the hardcoded endpoint http://31.97.137.157:45000/icons/116 and passes the response's credits field to the JavaScript Function constructor, executing the returned code with require, module, exports, process, Buffer, and other Node globals in scope. The destination is a bare IP on a non-standard port with no pinning, signing, or integrity verification; the executed content is fully attacker-controlled and mutable server-side. The package's metadata and identifiers frame the loader as a CDN icon fetcher (iconDomain, path = "/icons/", a bearrtoken: "logo" header, a font-awesome-shaped path, and an unused setDefaultModule referencing cdnjs/cloudflare/fastly), and the README advertises the package as a lightweight zero-dependency helper while dependencies include axios, express, better-sqlite3, @primno/dpapi, node-machine-id, and socket.io-client — a native-Windows-credential (DPAPI) plus persistent-socket stack inconsistent with an icon helper. Any code path that reaches getPlugin grants remote code execution on the consumer's host to the operator of 31.97.137.157.

Malicious versions

2 flagged

0.5.21.5.2

Indicators of compromise (SHA-256)

409198f5545f08b1a2102b5e2f5ec038f4a882d4c1088377f1fa7c4cc8bc37dd

82b68f964850d0777c1f3993c52e3b66dc425b02ee82fb33bcd958514f730926

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

Campaign

IN-MAL-2026-014799IN-MAL-2026-014810

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ventrix-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