Which versions of 01-0redi7qgbz0uv are malicious?

The following npm versions of 01-0redi7qgbz0uv are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate 01-0redi7qgbz0uv if I installed it?

01-0redi7qgbz0uv 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 01-0redi7qgbz0uv — how do I know if it already compromised me?

If 01-0redi7qgbz0uv was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is 01-0redi7qgbz0uv part of a known attack campaign?

Yes — 01-0redi7qgbz0uv is associated with the IN-MAL-2026-002418 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 01-0redi7qgbz0uv across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for 01-0redi7qgbz0uv (version 1.0.0).

Malicious package

01-0redi7qgbz0uvnpm

Advisory published May 12, 2026Updated May 13, 2026

01-0redi7qgbz0uv is a confirmed malicious npm package (MAL-2026-3666) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 01-0redi7qgbz0uv (npm)

MAL-2026-3666

Immediate action

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

npm uninstall 01-0redi7qgbz0uv

What this malware does

the analysis found that this package has a garbage randomized name ('01-0redi7qgbz0uv'), empty description, placeholder test script, and an index.js that is not valid JavaScript confirms hyphenated/numeric-leading identifiers that cannot be parsed). It has no functional code whatsoever. Its sole observable effect is to pin 40+ obscure wallet/crypto/trading-themed dependencies at 'latest' (walletgeninjsio, transferbwallets, balancetracking, arbitexchange, cryptoperfume, -rypto-ompareinfo, etc.). This matches the meta-package dependency-delivery pattern: the package itself contains no payload, but installing it forces installation of an arbitrary batch of attacker-controlled packages at whatever the latest version happens to be. Under the generic-placeholder-metadata-plus-network calibration (placeholder metadata + indirect supply-chain reach), combined with (a) non-functional entrypoint, (b) randomized name indicating no intended human consumer, and (c) crypto-themed transitive targets at floating 'latest' ranges, there is no legitimate use case for this package.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

5ceb633970757ab5d5ee0b64512c18d46be8402ac2169769101655a697ee5d6d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for 01-0redi7qgbz0uv (version 1.0.0).
If you installed it — respond
01-0redi7qgbz0uv 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 01-0redi7qgbz0uv was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. 01-0redi7qgbz0uv 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-002418

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks 01-0redi7qgbz0uv-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