Which versions of library-explorer are malicious?

The following npm versions of library-explorer are flagged malicious: 25.2.1. Treat any of these as compromised.

How do I remediate library-explorer if I installed it?

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

If library-explorer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is library-explorer part of a known attack campaign?

Yes — library-explorer is associated with the IN-MAL-2026-009759, RLMA-2026-05568, RLUA-2026-06304 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 library-explorer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for library-explorer (version 25.2.1).

Malicious package

library-explorernpm

Advisory published Jul 12, 2026Updated Sep 1, 2026

library-explorer is a confirmed malicious npm package (MAL-2026-10205) that opens a backdoor for remote access (malicious version 25.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in library-explorer (npm)

MAL-2026-10205

Immediate action

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

npm uninstall library-explorer

What this malware does

package.json declares preinstall: node index.js. On npm install, index.js collects installer host identity (os.hostname, os.platform, os.arch, os.homedir, os.userInfo username/uid/gid/shell, CPU/memory) and shells out whoami and (non-Windows) id via child_process.exec, then POSTs the aggregated JSON to a hardcoded Burp Collaborator subdomain at https://bgvge0daqrvkonl6x9qrx553ruxllb90.oastify.com/detox56. The package ships no real functionality (empty description/author, single preinstall script) and is consistent with a dependency-confusion / internal-name recon beacon staged to fire automatically on install.

Malicious versions

1 flagged

25.2.1

Indicators of compromise (SHA-256)

28b5db05b3bdfb9cc8b1af9759f05a3bc7a1b6a9c364b86831b93df78e9e2273

f6234e9b4c96ff0519f177478056bf8658e2de514ea555a4b3cd53f731bfb371

b487df7eb501228453247e1766c496a9f0359e6fbd2000a7a70ec243019dd554

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for library-explorer (version 25.2.1).
If you installed it — respond
library-explorer 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 library-explorer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. library-explorer on npm has been identified as a malicious package (version 25.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009759RLMA-2026-05568RLUA-2026-06304

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks library-explorer-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