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

@sarex-team/sdk-jsnpm

@sarex-team/sdk-js is a confirmed malicious npm package (MAL-2026-14204) that opens a backdoor for remote access (malicious version 9.9.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @sarex-team/sdk-js (npm)

MAL-2026-14204
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @sarex-team/sdk-js

What this malware does

Package declares scripts.install="node index.js", which top-level requires lib/core.js. lib/core.js reads os.userInfo().username, os.hostname(), and process.cwd(), joins them with a package tag and timestamp, and issues dns.resolve4() against a subdomain of oob.sl4x0.xyz — a DNS-tunneled beacon to an attacker-controlled out-of-band collector. The destination host oob.sl4x0.xyz and the Node API names (os, dns, userInfo, hostname, cwd, resolve4) are stored as hex byte arrays in lib/b02e30.js and lib/6ad264.js and reconstructed at runtime via String.fromCharCode to disguise the recon path. The beacon fires automatically on npm install and again on every require() of the package, with no user interaction required.

Malicious versions

1 flagged
9.9.11

Indicators of compromise (SHA-256)

3b599c4cb22f02d79a217a53a61243a08017783b2a8d41afaa59b46128d863c2

Detection & response playbook

Backdoor / remote access

  1. Find it

    Search your lockfiles and build artifacts for @sarex-team/sdk-js (version 9.9.11).

  2. If you installed it — respond

    @sarex-team/sdk-js 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.

  3. Did it already run?

    If @sarex-team/sdk-js 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. @sarex-team/sdk-js on npm has been identified as a malicious package (version 9.9.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018291

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @sarex-team/sdk-js-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
@sarex-team/sdk-js (npm) malicious package — MAL-2026-14204 | O3 Security