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

govapkgPyPI

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

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

What this malware does

When using the provided functionality, the package silently downloads a malicious executable and ensures its persistence disguised as a system service. The binary connects with telegra[.]ph. It appears that the contacted URL is built from the template https://api.telegra.ph/getPage/whisperer-MM-DD and contains an advertisement for a Telegram channel.

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

Campaign: 2026-07-govpkg

Reasons (based on the campaign):

  • Downloads and executes a remote executable.

  • action-hidden-in-lib-usage

  • persistence

Malicious versions

1 flagged
0.1.0

Indicators of compromise (SHA-256)

aa79a3120abb07b8e73d784c41300631c6a9b9654a653a916bddb4bb86bbc088
c23fe2f960316aca782b4319dac6f960d4397ec40428d34e28b1769cd0bff4b4

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

  2. If you installed it — respond

    govapkg 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 govapkg 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 govapkg 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. govapkg on PyPI has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-07-govpkg

References

Credits

  • Kamil Mańkowski (kam193) · reporter

Detect & block this

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