MAL-2026-13921 Malicious code in envpack-conf (npm)
Malicious package
Published
MAL-2026-13921 is a malicious package: envpack-conf (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-13921/ (Markdown: https://insights.sbomify.com/MAL-2026-13921/index.md)
- Package
- envpack-conf
- Registry
- npm
What is MAL-2026-13921?
MAL-2026-13921 is a malicious package in envpack-conf, published on 12 Aug 2026.
Official description
envpack-conf 1.0.1 is a trojanized copy of the pkg-conf utility. index.js appends a top-level async IIFE that runs whenever the module is imported. The IIFE queries public Ethereum RPC endpoints (eth.blockscout.com/api, 1rpc.io/eth, eth.drpc.org, ethereum-rpc.publicnode.com, eth-mainnet.public.blastapi.io) for transactions sent from the attacker address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, decodes the
to field of those transactions into two IPv4 addresses, fetches an XOR-encrypted second-stage payload from those hosts at path /0x/cls, and executes the decrypted payload with both eval() and spawn('node',['-e',<payload>],{detached:true,stdio:'ignore'}).unref(), giving a detached child process on the installer's host. Every sensitive identifier (module names http/https/zlib/child_process, hostnames, HTTP methods, header names, the attacker address, the RPC URLs, request paths, and global variable names) is written as \uXXXX-escaped literals to evade static analysis. The package name and README (devpack-conf) impersonate Sindre Sorhus's pkg-conf; package.json lists the author as 'Sinde Sorus' <[email protected]>, a typosquat of the real maintainer. The legitimate pkg-conf source is preserved above the injected block as cover.What should I do about MAL-2026-13921?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.