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

infogram-botPyPI

infogram-bot is a confirmed malicious PyPI package (MAL-2026-14131) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.2.0, 1.2.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in infogram-bot (PyPI)

MAL-2026-14131
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall infogram-bot

What this malware does

The package provides Telegram-based remote access to the machine it runs on. It was deliberately created and used to hack other machines, exfiltrate files and credentials.

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

Campaign: 2026-08-httpz-requests

Reasons (based on the campaign):

  • files-exfiltration

  • rat

  • persistence

  • uses-telegram-bot

  • obfuscation

  • native-extension

Malicious versions

11 flagged
1.0.01.2.01.2.11.3.01.4.01.5.01.6.01.6.11.7.01.8.01.9.0

Indicators of compromise (SHA-256)

454fa32963f58275e35167d59dd581240725e099682e76e44b6fca7b22332cb0

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

  2. If you installed it — respond

    infogram-bot 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 infogram-bot 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 infogram-bot 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. infogram-bot on PyPI has been identified as a malicious package (versions 1.0.0, 1.2.0, 1.2.1, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.6.1, and 3 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-08-httpz-requests

References

Credits

  • Kamil Mańkowski (kam193) · analyst

Detect & block this

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

Explore