Which versions of data-pipeline-check are malicious?

The following PyPI versions of data-pipeline-check are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate data-pipeline-check if I installed it?

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

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

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

Malicious package

data-pipeline-checkPyPI

Malicious code in data-pipeline-check (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-4271

Immediate action

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

pip uninstall data-pipeline-check

What this malware does

On import pipeline_check, the package spawns a daemon thread that, after a random 3-15 second delay, walks ~/.ssh, ~/.aws, ~/.ethereum, ~/.config, ~/.docker, ~/.kube, and the current working directory, regex-matching contents against patterns for private keys, BIP-39 mnemonics, OpenAI sk- keys, GitHub ghp_ tokens, AWS AKIA keys, and generic password patterns (pipeline_check/_core.py:18,:71). Matches are POSTed as JSON (with hostname, platform, cwd) to webhook URLs fetched at runtime from https://ddjidd564.github.io/defi-security-best-practices/config.json; the initial config fetch disables TLS verification via ssl.CERT_NONE and check_hostname=False (pipeline_check/_core.py:27-30,:62). The package's public surface (PipelineValidator, CLI) is cover-story code — __init__.py imports _scan_and_report from _core, so simply importing the module triggers the harvester. The randomized delay is evasion timing, and the remote-resolved webhook list lets the operator rotate exfil destinations without republishing.

During import, the package runs the code to exfiltrates credentials, private keys and other sensitive data.

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

Campaign: 2026-05-eth-security-auditor

Reasons (based on the campaign):

files-exfiltration
exfiltration-env-variables
crypto-related
Downloads and executes a remote malicious script.
exfiltration-crypto
exfiltration-credentials

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

7cd1ebfd030a45f91ca541aaec69795656342b54ccd092eecb7117adb89e7f63

37ca0e77c4eda50057aa04c615897f067ee866d02fc1e2fe65cdbb263d3081e8

7abf0994093a7a35df475ccc8b460ccb15b7f3ccba57f05f758a765e3e3da940

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

Campaign

2026-05-eth-security-auditorIN-MAL-2026-004426IN-MAL-2026-004425

References

Credits

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

Detect & block this

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