Malicious code in @sarex-team/sdk-js (npm)
Historical advisory saved 24 Oct 2026 13:17:17 UTC. The publisher may have updated it since then. Latest advisory.
osv · MAL-2026-14204
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (3b599c4cb22f02d79a217a53a61243a08017783b2a8d41afaa59b46128d863c2) 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.
- Source published
- 19 Aug 2026 02:31:33 UTC
- Source modified
- 19 Aug 2026 03:00:14 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.