Which versions of envpack-conf are malicious?

The following npm versions of envpack-conf are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate envpack-conf if I installed it?

envpack-conf establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed envpack-conf — how do I know if it already compromised me?

If envpack-conf 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 envpack-conf part of a known attack campaign?

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

Malicious package

envpack-confnpm

envpack-conf is a confirmed malicious npm package (MAL-2026-13921) that opens a backdoor for remote access (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in envpack-conf (npm)

MAL-2026-13921

Immediate action

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

npm uninstall envpack-conf

What this malware does

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.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

a061ac72b9e392fee182ad4873aab0cc9a64694a11228438a7838343b96d338f

df4b13486d2134e1bec02ca3519e60d721da2d320c37ad7c8ffe96f29799eb20

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for envpack-conf (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging envpack-conf across your stack and pipelines.
If you installed it — respond
envpack-conf establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If envpack-conf 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 envpack-conf 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. envpack-conf on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017609IN-MAL-2026-017617

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks envpack-conf-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database