Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

xblaxwnpm

Advisory published Updated

xblaxw is a confirmed malicious npm package (MAL-2026-17708) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.1.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in xblaxw (npm)

MAL-2026-17708
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall xblaxw

What this malware does

[email protected] is a stub package whose only behavior is a beacon. The package.json postinstall script runs node beacon.cjs, which collects host identifiers (hostname, install path, process.cwd(), process.version) and POSTs them as JSON to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc over plaintext HTTP. The same beacon is re-fired on require(): index.js exports a Proxy that returns a no-op function for any property access and calls require('./beacon.cjs').fire() on load, so the exfiltration also triggers whenever a consumer imports the package. The package description is 'Compatibility shim.' with no real functionality — the Proxy-of-noops export is consistent with a dependency-confusion / name-squat beacon designed to confirm which internal names resolve to this public package and report back installer host metadata to the operator at 185.158.107.175:8787.

Malicious versions

7 flagged
1.0.01.0.11.1.02.0.02.0.13.0.099.0.1

Indicators of compromise (SHA-256)

110314989632807fad14e5fd2256199e22923b20df9f841ef8cce1480f13a693
992dbd421e3f64461b699aa41190af6729174ecf2a179e5986aa8c638bea4ba7
a67740f8c8fac71eb25c053bf07b93f3bc7b699aca1889831c2d64633e4f9d45
cc6a7f374924e3a4dc464dff2a51b6e916645280b776768d77fce9b0cd060045
e92f858a6d813c2230dd5be0f27dba62ea7a966f1993443ebdd319b6d2a6da2c
19bf74581564f1973f91f22b5ec0c562ba39e57b339306745910dba75f3a9367
2d2e0b35582727d314517ea66b234f665258076783678cdf645075a7294a0aed

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for xblaxw (7 malicious versions).

  2. If you installed it — respond

    xblaxw is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If xblaxw 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. xblaxw on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.1.0, 2.0.0, 2.0.1, 3.0.0, 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021236IN-MAL-2026-021241IN-MAL-2026-021265IN-MAL-2026-021240IN-MAL-2026-021244IN-MAL-2026-021242IN-MAL-2026-021243

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks xblaxw-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

xblaxw (npm) malicious package — MAL-2026-17708 | O3 Security