Which versions of devpack-conf are malicious?

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

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

devpack-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 devpack-conf — how do I know if it already compromised me?

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

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

Malicious package

devpack-confnpm

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

Malicious code in devpack-conf (npm)

MAL-2026-12177

Immediate action

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

npm uninstall devpack-conf

What this malware does

[email protected] is a typosquat of pkg-conf. index.js contains a top-level eval(atob(...)) that decodes an obfuscated loader. The loader queries Ethereum RPC/blockscout endpoints for transactions from the hardcoded address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, extracts an IPv4 address from the transaction's to field, fetches an XOR-encoded payload from http://<resolved-ip>:443/0x/cls and /0x/ls (XOR key delivered via the x-payload-b64 response header), eval()s the decrypted payload, and spawns a detached node -e <payload> child process with stdio:'ignore' and windowsHide:true. Sensitive strings (http, https, child_process, spawn, endpoint paths) are hidden behind \u unicode escapes. The malicious code executes automatically at require/import time on any consumer of the package.

Malicious versions

1 flagged

5.0.0

Indicators of compromise (SHA-256)

fabc4baeb912d72d08ef42d8b6b5e147b1f7dc18fc01e796bc6ac17f1c7dff68

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

Campaign

IN-MAL-2026-014434

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devpack-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