Which versions of vexium-kit are malicious?

The following npm versions of vexium-kit are flagged malicious: 2.0.2, 10.0.2. Treat any of these as compromised.

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

Remove vexium-kit from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed vexium-kit — how do I know if it already compromised me?

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

Yes — vexium-kit is associated with the IN-MAL-2026-017661, IN-MAL-2026-017666 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 vexium-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 vexium-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 vexium-kit across your stack and pipelines.

Malicious package

vexium-kitnpm

vexium-kit is a confirmed malicious npm package (MAL-2026-13963) that executes malicious code on install (malicious versions 2.0.2, 10.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vexium-kit (npm)

MAL-2026-13963

Immediate action

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

npm uninstall vexium-kit

What this malware does

On require, index.js issues an HTTPS request to the hardcoded bare-IP endpoint https://31.97.137.157:45000/icons/116 and passes the response's credits field to new Function('require','module',...,'Promise', data.credits), executing operator-controlled JavaScript with require, process, and Buffer in scope. The remote-eval sink is named getPlugin, accompanied by an unused setDefaultModule decoy referencing font-awesome CDN paths, while the README advertises the package as a zero-dependency utility toolkit. Declared dependencies (@primno/dpapi, better-sqlite3, sqlite3, node-machine-id) match the toolkit shape used to decrypt Chromium DPAPI-protected cookies/passwords and read browser Login Data databases, indicating the operator-supplied payload's intended follow-on capability against the installer.

Malicious versions

2 flagged

2.0.210.0.2

Indicators of compromise (SHA-256)

1686bf2bc5c03717c87c1ff5447e2fc11aa6d2e976e1b14e5edcace286829100

81256cad9a270a808ce5e9cb2d6987aef06c2c236baa7ae76b8172c40ee61dd9

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vexium-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 vexium-kit across your stack and pipelines.
If you installed it — respond
Remove vexium-kit from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If vexium-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 vexium-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. vexium-kit on npm has been identified as a malicious package (versions 2.0.2, 10.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017661IN-MAL-2026-017666

References

Credits

Amazon Inspector · finder

Detect & block this

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