Which versions of pyrogrqm are malicious?

The following PyPI versions of pyrogrqm are flagged malicious: 0.3. Treat any of these as compromised.

How do I remediate pyrogrqm if I installed it?

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

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

Yes — pyrogrqm is associated with the 2025-10-speedd-testing-bot 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 pyrogrqm 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 pyrogrqm (version 0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pyrogrqm across your stack and pipelines.

Malicious package

pyrogrqmPyPI

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

MAL-2025-193010

Immediate action

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

pip uninstall pyrogrqm

What this malware does

The package, distinguished as a speed testing or typosquatted Telegram library, contains a Telegram bot to perform remote control of the computer

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-10-speedd-testing-bot

Reasons (based on the campaign):

rat
Downloads and executes a remote malicious script.
typosquatting

Malicious versions

1 flagged

0.3

Indicators of compromise (SHA-256)

02c3334952bcf80c0523b20a24f0b744463a944a4f3d18dc45a3f3c1bd00c1eb

3984bd457f261487b6328e55df7adc889a9b2457fb24e0dc118118334436e34e

fce6bd86719efe640ecbf0e31e7d87bcaf307e6364ab6078c7e14c035a532339

689396922f7c033b925ee5a59ca0e2c10d69a982a2c90a73c44c1a322795f0bc

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

Campaign

2025-10-speedd-testing-bot

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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