Which versions of groq-mcp are malicious?

The following PyPI versions of groq-mcp are flagged malicious: 0.0.1, 9.9.9. Treat any of these as compromised.

How do I remediate groq-mcp if I installed it?

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

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

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

Malicious package

groq-mcpPyPI

Malicious code in groq-mcp (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6007

Immediate action

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

pip uninstall groq-mcp

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.

The OpenSSF Package Analysis project identified 'groq-mcp' @ 9.9.9 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

0.0.19.9.9

Indicators of compromise (SHA-256)

b7952d7703221f736f36b232e942803539ca0ebf66b1c2aaec2ab61ea6322a3c

fc413b596aae50402d046f5c014166dcdf6224cbd1e0747f115afabf40ba9aa0

3bce71434ebf3069c03ca9d1ec208c7a2a59c434ba1a3eff63d31a60cbf32c71

f310f1669db9ce74e36d92085a6a67098f7c0ee086d8da5998b709d565a3fe12

8a06702c9112febb789f6b893da3c506199aadc17eefb5b9ee940ebde77c751c

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

Campaign

GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks groq-mcp-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