Malicious code in @sarex-team/sdk-js (npm)
@sarex-team/sdk-js npm package contained malicious code that exfiltrated system information (username, hostname, working directory) via DNS tunneling to an attacker-controlled domain (oob.sl4x0.xyz) on every install and require() call.
- Disclosed
- Last updated
- Blast radius
- All npm users who installed @sarex-team/sdk-js
- Ecosystems
- Attack vectors
- Affected entities
- @sarex-team/sdk-js
The npm package @sarex-team/sdk-js contained malicious code designed to perform reconnaissance and exfiltrate system information. The package declared a scripts.install hook that executed node index.js, which required lib/core.js and triggered the malicious behavior.\n\nThe malicious code collected sensitive system information including the current user's username, hostname, and working directory. This data was combined with a package tag and timestamp, then exfiltrated via DNS resolution queries to subdomains of oob.sl4x0.xyz, an attacker-controlled out-of-band data collector. The DNS tunneling technique allowed data exfiltration without obvious network traffic.\n\nTo evade detection, the attacker obfuscated API names and domain references by storing them as hex byte arrays in lib/b02e30.js and lib/6ad264.js, reconstructing them at runtime using String.fromCharCode. The beacon executed automatically during npm install and on every subsequent require() of the package, requiring no user interaction.\n\nThe malicious package was identified by Amazon Inspector and credited to the OpenSSF malicious-packages project.
Indicators of compromise
- Packages
- @sarex-team/sdk-js
- Domains
- oob.sl4x0.xyz
Remediation
- Immediately uninstall @sarex-team/sdk-js from all systems
- Audit npm install logs and package-lock.json files to identify affected installations
- Review system logs for suspicious DNS queries to oob.sl4x0.xyz and related subdomains
- Assume compromise of any system that installed this package; rotate credentials and review for unauthorized access
- Update npm dependencies to remove this package and use legitimate alternatives
- Monitor for similar obfuscation patterns in dependencies
Sources
- GitHub Advisory GHSA-44g3-f495-wrr5 · GitHub Advisory Database
Cite this entry
"Malicious code in @sarex-team/sdk-js (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 19, 2026; last updated August 19, 2026. https://supplychainattack.org/incident/malicious-code-in-sarex-team-sdk-js-npm-1wnfpc
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in 3-buildsight-web (npm)
The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.
npmCompromised package - resolvedcritical
Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)
Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in create-coin (npm)
create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in @syncraft-labs/vue (npm)
The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.
npmCompromised package