Which versions of @leonardo0902/vortex-kit are malicious?

The following npm versions of @leonardo0902/vortex-kit are flagged malicious: 12.0.2. Treat any of these as compromised.

How do I remediate @leonardo0902/vortex-kit if I installed it?

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

If @leonardo0902/vortex-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 @leonardo0902/vortex-kit part of a known attack campaign?

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

Malicious package

@leonardo0902/vortex-kitnpm

@leonardo0902/vortex-kit is a confirmed malicious npm package (MAL-2026-13939) that steals credentials and exfiltrates sensitive data (malicious version 12.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @leonardo0902/vortex-kit (npm)

MAL-2026-13939

Immediate action

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

npm uninstall @leonardo0902/vortex-kit

What this malware does

The main module in @leonardo0902/[email protected] issues an HTTPS request to a hardcoded bare-IP endpoint at 31.97.137.157:45000/icons/116 and passes the returned credits field to new Function('require',..., 'Promise', data.credits), executing attacker-controlled JavaScript with full Node context (require, process, Buffer) whenever the module is loaded and its exported function is invoked. The fetch destination is disguised as a static-asset endpoint: the file defines a decoy setDefaultModule referencing legitimate CDNs (cloudflare, fastly, akamai, cloudfront) and a font-awesome path, then reuses the identical variable names (protocol, domain, path, head, bearrtoken: 'logo') around the bare-IP fetch-and-eval to frame it as an icon download. Bundled native dependencies (@primno/dpapi, better-sqlite3, node-machine-id) are consistent with a dynamically delivered browser-credential-stealer payload. The remote code is unpinned, unverified, and controlled entirely by whoever operates the IP.

Malicious versions

1 flagged

12.0.2

Indicators of compromise (SHA-256)

1707e031a6c470479ecbd0b01a480cc801a9d049a3732abc265ccad8791272a9

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

Campaign

IN-MAL-2026-017663

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @leonardo0902/vortex-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