Which versions of xapi-lib are malicious?

The following npm versions of xapi-lib are flagged malicious: 88.2.3, 88.2.5, 90.2.1, 90.3.1. Treat any of these as compromised.

How do I remediate xapi-lib if I installed it?

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

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

Yes — xapi-lib is associated with the IN-MAL-2026-021504, IN-MAL-2026-021505, IN-MAL-2026-021502, IN-MAL-2026-021503 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 xapi-lib across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for xapi-lib (4 malicious versions).

Malicious package

xapi-libnpm

Advisory published Oct 15, 2026Updated Oct 16, 2026

xapi-lib is a confirmed malicious npm package (MAL-2026-17896) that opens a backdoor for remote access (malicious versions 88.2.3, 88.2.5, 90.2.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in xapi-lib (npm)

MAL-2026-17896

Immediate action

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

npm uninstall xapi-lib

What this malware does

[email protected], 88.2.5, 90.2.1, and 90.3.1 describes itself as a package for getting IP location and metadata. Its preinstall hook runs node index.js on npm install and requests https://realwbx.com/ip.php?ip=8.8.8.8 with the hardcoded Authorization value fa79878bc2cfb48bd5127ae26fb661b1, which is the same in all four versions and differs from the value in each of the account's other packages. The npm account conx3993 published xapi-lib on 2026-10-15, one of 9 packages from that account between 2026-09-30 and 2026-10-15 whose preinstall hook calls realwbx.com.

[email protected] declares preinstall: node index.js in package.json, and index.js performs an unconditional top-level HTTPS GET to realwbx.com/ip.php (passing 8.8.8.8 and a hardcoded Authorization header) on load. The call fires automatically during npm install, sending the installer's source IP to a hardcoded non-publisher endpoint unrelated to any advertised functionality. The package itself is a one-file stub with no library content, so dependency resolution plus the preinstall beacon is the entire effect of installing it. The destination realwbx.com is not a publisher-aligned domain, the request is not caller-configurable, and no documentation discloses the outbound call.

Malicious versions

4 flagged

88.2.388.2.590.2.190.3.1

Indicators of compromise (SHA-256)

08fefb7bcc7ef9e212432c91ec73a326965240fdbcb7782e3d2fb61155fe6d45

beac62be73c115f383ea095cc364879294d6c105817d3c0eb6bfb30ce7bcf46c

c2cad7956f6504f2fefff4ce1a2a3309660ebcc8dd6858f41085f478ad5909ef

e82133a7b4558aea71dd4629832347ac615573b581ee941960ab4b0244781779

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for xapi-lib (4 malicious versions).
If you installed it — respond
xapi-lib 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 xapi-lib 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. xapi-lib on npm has been identified as a malicious package (versions 88.2.3, 88.2.5, 90.2.1, 90.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021504IN-MAL-2026-021505IN-MAL-2026-021502IN-MAL-2026-021503

References

Credits

Amazon Inspector · finder
InvisiRisk, Inc. · finder

Detect & block this

O3 blocks xapi-lib-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