Which versions of llmgenerator are malicious?

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

How do I remediate llmgenerator if I installed it?

llmgenerator 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 llmgenerator — how do I know if it already compromised me?

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

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

Malicious package

llmgeneratorPyPI

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

MAL-2026-5770

Immediate action

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

pip uninstall llmgenerator

What this malware does

On pip install, setup.py performs an HTTP GET to https://pastebin.com/raw/yBcUM1QB, takes the first line of the response body, and passes it to os.system(f'cmd /c "{cmd_pastebin}"'). The fetched content is mutable, anonymous, and unauthenticated — the author can change what runs on every installer's machine at any time without republishing the package. The package ships no functional Python code (src/ contains only an empty.egg-info directory), confirming the package exists solely as a vehicle for the install-time dropper. The package name impersonates an LLM-tooling brand to attract installs. Installing this package grants arbitrary shell execution on the installer's Windows machine.

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)

1948e85cdc950b3661b64655a2c0cc73708ecf6e409d19a77089e4089864411a

06e55ac2d3368516d538c8efaad2b83814dbb61813f36ab5655f77677ca0d6be

73050507e6d65ae0abcb9a0920fb9c13a31a0b8f776410020a35f11c0f332902

1039ac9ddb2b38917ea420c8b0c0e83dcf085cb1a49c37cd47745888ac3fb6cc

e5299b1bd4a72376cc08afbcb871276d2e1cfab5cdd5c10bd70236cc1be75baa

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 llmgenerator (version 2.21). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging llmgenerator across your stack and pipelines.
If you installed it — respond
llmgenerator 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 llmgenerator 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 llmgenerator 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. llmgenerator 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-006694

References

Credits

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

Detect & block this

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