MAL-2026-3666 Malicious code in 01-0redi7qgbz0uv (npm)
Malicious package
Published
MAL-2026-3666 is a malicious package: 01-0redi7qgbz0uv (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-3666/ (Markdown: https://insights.sbomify.com/MAL-2026-3666/index.md)
- Package
- 01-0redi7qgbz0uv
- Registry
- npm
What is MAL-2026-3666?
MAL-2026-3666 is a malicious package in 01-0redi7qgbz0uv, published on 12 May 2026.
Official description
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.
What should I do about MAL-2026-3666?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.