Which versions of webdev-conf are malicious?

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

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

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

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

Yes — webdev-conf is associated with the IN-MAL-2026-011359 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 webdev-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 webdev-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 webdev-conf across your stack and pipelines.

Malicious package

webdev-confnpm

webdev-conf is a confirmed malicious npm package (MAL-2026-12005) 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 webdev-conf (npm)

MAL-2026-12005

Immediate action

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

npm uninstall webdev-conf

What this malware does

[email protected] is a typosquat of the sindresorhus/pkg-conf library, published under author 'Sinde Sorus' [email protected] (homoglyph of Sindre Sorhus). index.js appends an eval(atob(...)) block after the legitimate library code. On require(), the decoded payload queries public Ethereum RPC endpoints and blockscout.com/api for the latest transaction sent from the attacker address 0xa322E5f3D311D3080e6f01210263e9aDC2490Ef1, extracts an IP address from that transaction, then fetches XOR-encrypted next-stage JavaScript from http://<IP>:443/0x/cls and http://<IP>:443/0x/ls, eval()s it in-process, and re-executes it via spawn('node', ['-e', payload], {detached:true, windowsHide:true}).unref(). Identifiers such as http, https, child_process, spawn, and the RPC URLs are hidden with \uXXXX unicode escapes. The C2 IP is rotatable by the attacker via on-chain transactions (EtherHiding technique). Any package that require()s webdev-conf triggers remote code execution on the installer's host.

Malicious versions

1 flagged

5.0.0

Indicators of compromise (SHA-256)

9577d9f40486af224c5dd365ffbab6a5d45c4a052dfe6de50bc1d8f130d9642a

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 webdev-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 webdev-conf across your stack and pipelines.
If you installed it — respond
webdev-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 webdev-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 webdev-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. webdev-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-011359

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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