crypt0co-walet-poc
This report shows the evidence for crypt0co-walet-poc@1.0.0, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-4540 confirms this npm version as malicious.
Advisory
MAL-2026-4540
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in crypt0co-walet-poc (npm)
Details
On require/import, index.js (lines 6-12) serializes the full process.env to /tmp/poc_impact.json and runs `whoami` and `ip addr` via execSync to fingerprint the host. Any consumer that imports this package leaks every environment variable available to the Node process — on CI and developer machines this routinely includes cloud credentials, npm/GitHub tokens, and other secrets — into a predictable, world-readable path in /tmp where any local user or subsequent process can read them. The package name `crypt0co-walet-poc` uses character substitutions (`0` for `o`, `walet` for `wallet`) consistent with impersonation of crypto-wallet packages, and the code self-labels as `CRITICAL IMPACT POC P0`. Author metadata fields (description, keywords, author) are empty. Even if the publisher's stated intent is bug-bounty research, the installer harm — full environment dump plus recon command execution at import time — is real and unconsented.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to crypt0co-walet-poc@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing crypt0co-walet-poc@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.