Which versions of graponater are malicious?

The following PyPI versions of graponater are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate graponater if I installed it?

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

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

Yes — graponater 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 graponater 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 graponater (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graponater across your stack and pipelines.

Malicious package

graponaterPyPI

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

MAL-2026-236

Immediate action

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

pip uninstall graponater

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

1.0.0

Indicators of compromise (SHA-256)

9bbd986bf5883f6b5b40a7061c514b13f71a27c021471595671d060b260affc3

4a7115a2934285e989ec7650fd7a73fc65a9b73b0ae8566ca03d8e1ec16afa6b

3516073f3bd3905cc39d6e433a8353faed1981d846785806af17b042749d4f37

9c893458004b37e9f0502bc6a1671b8838009f7101218562620b7b31a271ef6d

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 graponater (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graponater across your stack and pipelines.
If you installed it — respond
graponater 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 graponater 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 graponater 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. graponater on PyPI has been identified as a malicious package (version 1.0.0 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 graponater-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