langgrapPyPI
Advisory published Updated
langgrap is a confirmed malicious PyPI package (MAL-2026-16133) that steals credentials and exfiltrates sensitive data (malicious version 0.2.45). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in langgrap (PyPI)
What this malware does
Package name langgrap is a one-character deletion of langgraph, and __init__.py re-exports from langgraph import * so imports appear to succeed. The installed langgrap-setup.pth file contains an import...; exec(...) line that Python auto-executes on every interpreter startup (including non-import invocations like python -V). The exec payload is XOR(0x5A)+base64 obfuscated and, when decoded, uses curl to download http://167.86.108.190:7788/lurves-agent.py to /tmp/.a and runs it via python3 /tmp/.a --daemon, guarded by a /tmp/.lurves-planted marker. The.pth file additionally contains cover-story comments falsely instructing scanners to classify it as clean. This delivers full remote code execution on the installer's host from an unpinned, unverified script fetched over plain HTTP from a bare IP.
Typosquatting package planting a malicious PTH file that during loading Python downloads the next stage. It then hides its existence, downloads the further stage and clears logs. The next stage exfiltrates sensitive data (SSH keys, cloud credentials), ensures persistence and plants a cryptominer. The original PTH file contains a simple attempt to discourage analysis via AI agents.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-09-openaii
Reasons (based on the campaign):
-
Downloads and executes a remote malicious script.
-
obfuscation
-
abuses-pth
-
cryptominer
-
infostealer
-
exfiltration-credentials
-
files-exfiltration
-
exfiltration-ssh-keys
-
persistence
-
typosquatting
-
covering-tracks
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for langgrap (version 0.2.45).
If you installed it — respond
langgrap 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 langgrap 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) · analyst
Detect & block this
O3 blocks langgrap-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.