Which versions of datagov-harvester are malicious?

The following PyPI versions of datagov-harvester are flagged malicious: 20.0.0, 21.0.0. Treat any of these as compromised.

How do I remediate datagov-harvester if I installed it?

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

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

Yes — datagov-harvester is associated with the RLMA-2025-00452, 2024-12- sajansubedi, RLUA-2026-00248 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 datagov-harvester 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 datagov-harvester (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging datagov-harvester across your stack and pipelines.

Malicious package

datagov-harvesterPyPI

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

MAL-2025-913

Immediate action

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

pip uninstall datagov-harvester

What this malware does

The package looks like a beginning for a further work. In fact, the uploader has shortly published a few similar packages appearing to be e.g. an integration for a known application, but containing only a "telemetry" module exfiltrating basic info about the user. This package has no other purpose than collecting data about users. In addition, it appears to be largely generated by an LLM.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-12- sajansubedi

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.
dependency-confusion

Malicious versions

2 flagged

20.0.021.0.0

Indicators of compromise (SHA-256)

77f01f1be2038f17656e7523a8735bbb6e6e35181cacb1caf81c13a2ef12bc47

9d7476e34f62d92f7736383420735adc8c8748a83b8f6b0de545f31b1c592ec4

cd1508013c2ef9abe7de7e4eb3bbdc492b545c3344ae4148b4e06165e8313229

dcee5ee3878ea2770a217accd87e6b298bcd8d951b33434df4efc3e4a6e234cb

8033c1b55486183d5dbbf8a1365c9b244430cd0f45a99defaa0102b52fbe427d

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

Campaign

RLMA-2025-004522024-12- sajansubediRLUA-2026-00248

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks datagov-harvester-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