Which versions of opengrep are malicious?

The following PyPI versions of opengrep are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8. Treat any of these as compromised.

How do I remediate opengrep if I installed it?

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

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

Yes — opengrep is associated with the RLMA-2025-01979, GENERIC-standard-pypi-install-pentest, RLUA-2026-00568 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 opengrep 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 opengrep (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging opengrep across your stack and pipelines.

Malicious package

opengrepPyPI

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

MAL-2025-2981

Immediate action

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

pip uninstall opengrep

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

8 flagged

0.0.10.0.20.0.30.0.40.0.50.0.60.0.70.0.8

Indicators of compromise (SHA-256)

12fb5927afd9ba0a8bc1d2b0f72af5e2eb2f0d8202e999da6f401ac3cca7f1b8

9454f71a434109877ff922804db2d081c4f08af5b047b0ee7a651ea21a0cf0fd

8de001a262d51e9750f84bfa2f6d30f5798aca9d0614b5feb95215ed1ced0507

ff192c815669701bedb4d6ee5c22adacb91a9be0db1204710cd3e83b871cb9fd

a7c4bbde4e0371dc055b22ffc8f525625c91f804b2f9aa9cb7af8d803efdd46c

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 opengrep (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging opengrep across your stack and pipelines.
If you installed it — respond
opengrep 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 opengrep 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 opengrep 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. opengrep on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-01979GENERIC-standard-pypi-install-pentestRLUA-2026-00568

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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