Which versions of govpkg are malicious?

The following PyPI versions of govpkg are flagged malicious: 0.1.0, 0.2.0. Treat any of these as compromised.

How do I remediate govpkg if I installed it?

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

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

Yes — govpkg is associated with the 2026-07-govpkg, IN-MAL-2026-010905 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 govpkg 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 govpkg (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging govpkg across your stack and pipelines.

Malicious package

govpkgPyPI

govpkg is a confirmed malicious PyPI package (MAL-2026-10770) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in govpkg (PyPI)

MAL-2026-10770

Immediate action

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

pip uninstall govpkg

What this malware does

Every public API function in govpkg (get, package, module) invokes a helper named normalizeHelper() that downloads an unpinned, unverified binary from the anonymous file-sharing host temp.sh (https://temp.sh/reaJk/client) to ~/.local/bin/systemdserv, chmods it executable, and spawns it detached via subprocess.Popen with start_new_session=True. The same helper writes an XDG autostart entry at ~/.config/autostart/systemdserv.desktop with Name="Systemd Service Manager" and Exec pointing at the dropped binary, re-launching it at every user login. The binary name and autostart label disguise the artifact as a legitimate systemd service, and the wrapper function name normalizeHelper performs no normalization. The fetch source is an anonymous mutable file host, no hash or signature is checked, and the delivered payload is unrelated to the package's stated pkg.go.dev client purpose.

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

2 flagged

0.1.00.2.0

Indicators of compromise (SHA-256)

736ef874636ee77d0a5007dea41ad6329e0d5523bfeb5254930985f451a6f6f6

355f6a84eb8df26cfd07042ce7a8f93bf9e1b565828eb3190215b804ed61e9d5

b6bce12d912d5250f59d801962a209655b085b6b35d9603e7cd23e9365728f9d

bcc7609ef2380436c805298b1d10362d361ea93b448db92433e3e69cc2de8ed8

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

Campaign

2026-07-govpkgIN-MAL-2026-010905

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database