Which versions of data-harvester are malicious?

The following PyPI versions of data-harvester are flagged malicious: 0.3.1. Treat any of these as compromised.

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

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

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

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

Malicious package

data-harvesterPyPI

data-harvester is a confirmed malicious PyPI package (MAL-2026-10191) that steals credentials and exfiltrates sensitive data (malicious version 0.3.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in data-harvester (PyPI)

MAL-2026-10191

Immediate action

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

pip uninstall data-harvester

What this malware does

On first import, data_harvester/init.py decodes a base64-embedded ~486KB Linux ELF, writes it to ~/.config/.npm-cache/snapd-network, sets mode 0777, and installs a user crontab entry (0 */12 * * *) to re-execute it every 12 hours. The binary is disguised under a system-service-like name in a hidden.npm-cache directory that maps to no real npm or snapd path. The init code then recursively removes the package's own dist-info/egg-info and pycache directories, erasing evidence while the dropped binary and cron entry persist.

The package embeds an executable stealing cryptocurrency wallets data. During import, code saves the executable under a name suggesting system utility and configures cron to run it periodically. The exfiltrated data is encrypted using embedded RSA code before uploading to file-sharing services or IPFS.

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

Campaign: 2026-07-py-base58

Reasons (based on the campaign):

crypto-related
exfiltration-crypto
persistence

Malicious versions

1 flagged

0.3.1

Indicators of compromise (SHA-256)

d9ff3c2a82fba71167baaab535551bcb60a32bf4eb1bdd355ef3314d493771c4

21c2e2c21d9afac9277d95589962d33a09651a5b6ef7e0b3c9e07aee56af213f

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

Campaign

2026-07-py-base58IN-MAL-2026-009820

References

Credits

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

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database