Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

gandon-pidar1PyPI

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

MAL-2025-928
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall gandon-pidar1

What this malware does

Package uses the template from https://github.com/thegoodhackertv/malpip to explore building malicious PyPI packages.

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

Campaign: SCRIPT_KIDDIE-thegoodhacker-paquete

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.

  • Package uses simple pre-prepared tools to create a low-quality malicious action.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

459830a44bb5c0991c28d4df53b69eaf4c4e7ae746a02e5967e418df4e04865a
5a56dbc76ac6858e10e5fe22e5dae8207b19403e578ac85fc1bebe80e96cbaf4
4ac6e5875e2e378713032cdf0e35f5eef05d5f3967b4ec5e8c57759adb128b21
fe8e8666110a162143a582dbfc5a6c6acf8d25ac937edfa9a9aaa8d32d28f10e
cd42cc227905f8f63b388c8f947c3c0cfd337827cd9c42da299d5b557f7682df

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for gandon-pidar1 (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 gandon-pidar1 across your stack and pipelines.

  2. If you installed it — respond

    gandon-pidar1 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.

  3. Did it already run?

    If gandon-pidar1 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.

  4. How O3 protects you

    O3 blocks gandon-pidar1 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. gandon-pidar1 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

RLMA-2025-00467SCRIPT_KIDDIE-thegoodhacker-paqueteRLUA-2026-00346

References

Credits

  • Kamil Mańkowski (kam193)
  • ReversingLabs · finder

Detect & block this

O3 blocks gandon-pidar1-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

gandon-pidar1 (PyPI) malicious package — MAL-2025-928 | O3 Security