Which versions of webrix-docs are malicious?

The following npm versions of webrix-docs are flagged malicious: 20.2.11. Treat any of these as compromised.

How do I remediate webrix-docs if I installed it?

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

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

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

Malicious package

webrix-docsnpm

Malicious code in webrix-docs (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10080

Immediate action

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

npm uninstall webrix-docs

What this malware does

package.json declares preinstall: node index.js, which runs automatically on npm install. index.js collects host reconnaissance data — os.hostname(), os.userInfo() (username, uid, gid, homedir), process.platform, cwd, and the output of whoami/id spawned via child_process — and POSTs it as JSON to the hardcoded URL https://c7kfuaf25guwigaz6r03kxet0k6bu3is.oastify.com/detox56 (a Burp Collaborator / oastify.com out-of-band interaction subdomain). The package has an empty description and author, no library code, and a name that mimics the legitimate webrix UI library — consistent with a typosquat/dependency-confusion lure whose only purpose is the install-time beacon.

Malicious versions

1 flagged

20.2.11

Indicators of compromise (SHA-256)

bec06de7c68db5cdd90e4b05be057a583f1a2318174916af07ed86d52a5011fc

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

Campaign

IN-MAL-2026-009220

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks webrix-docs-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