Which versions of ezllmgen are malicious?

The following PyPI versions of ezllmgen are flagged malicious: 2.21. Treat any of these as compromised.

How do I remediate ezllmgen if I installed it?

ezllmgen is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

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

Malicious package

ezllmgenPyPI

Malicious code in ezllmgen (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-5769

Immediate action

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

pip uninstall ezllmgen

What this malware does

setup.py downloads the first line of https://pastebin.com/raw/yBcUM1QB via urllib and passes it directly to os.system(f'cmd /c "{cmd_pastebin}"') during package installation. The Pastebin source is anonymous and author-mutable, so any installer running pip install EzLLMGen unconditionally executes whatever shell command is currently posted there, with no pinning, hash check, or signature. The package ships no Python modules — the src tree contains only an egg-info directory and the PKG-INFO metadata is placeholder text (Name/Author/Summary all set to 'EzLLMGen'), so there is no legitimate functionality to balance against the dropper. The install-time fetch-and-execute is the package's sole purpose.

During installation, the code attempts to download and start a malicious executable.

Likely related to 2025-08-raknet-testing-package.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-06-easyaillm

Reasons (based on the campaign):

Downloads and executes a remote executable.
obfuscation
malware
tool:mshta

Malicious versions

1 flagged

2.21

Indicators of compromise (SHA-256)

df46ebbf6c4ca141bceb389177692ad5c3465a0a567dcf5f687e3d00d707e655

d9ad551d9ee9ad2f3c29daab0377c3e52289324e938e28a3b58d71c60e8e15e8

7eb3715b5028be7e4532249383252c9143399fbb19dc222652dfa561b917f906

f9f4fb874a6b955c91d3355c7566a2798aeaf40e108ef9059cca61800a03bea5

7cc70e1a292c4903085d05b91ff1e5301e10e8d37d9299cd32dee637a27f3ac8

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ezllmgen (version 2.21). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ezllmgen across your stack and pipelines.
If you installed it — respond
ezllmgen is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If ezllmgen 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 ezllmgen 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. ezllmgen on PyPI has been identified as a malicious package (version 2.21 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-06-easyaillmIN-MAL-2026-006692

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks ezllmgen-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring