Which versions of langgrap are malicious?

The following PyPI versions of langgrap are flagged malicious: 0.2.45. Treat any of these as compromised.

How do I remediate langgrap if I installed it?

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.

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

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

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

Malicious package

langgrapPyPI

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)

MAL-2026-16133

Immediate action

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

pip uninstall langgrap

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

1 flagged

0.2.45

Indicators of compromise (SHA-256)

80943fa86afe1c0cd0b657339f2125c48de0ca3cf9848b895e2e60ea744b1db9

b11e221d911cf4904a1508f284da0ac0eb17a88e91dadb6dc60ef3bc5d547380

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 langgrap (version 0.2.45). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging langgrap across your stack and pipelines.
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 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 langgrap 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. langgrap on PyPI has been identified as a malicious package (version 0.2.45 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-09-openaiiIN-MAL-2026-020006

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database