Which versions of crypt0co-walet-poc are malicious?

The following npm versions of crypt0co-walet-poc are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate crypt0co-walet-poc if I installed it?

crypt0co-walet-poc 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 crypt0co-walet-poc — how do I know if it already compromised me?

If crypt0co-walet-poc 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 crypt0co-walet-poc part of a known attack campaign?

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

Malicious package

crypt0co-walet-pocnpm

Malicious code in crypt0co-walet-poc (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4540

Immediate action

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

npm uninstall crypt0co-walet-poc

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

b5510d98b1e380f6c130bf9b4428321d711ae88d8a4fcb66368a2f6fb4e7ff58

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

Campaign

IN-MAL-2026-004052

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks crypt0co-walet-poc-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