Malicious code in @sarex-team/sdk-js (npm)
The npm package @sarex-team/sdk-js version 9.9.11 contains malicious code that executes automatically upon installation and usage. It collects system information such as username, hostname, and current working directory, then sends this data via DNS requests to an attacker-controlled domain. The malicious behavior is obfuscated by storing key strings as hex byte arrays and reconstructing them at runtime. This results in a DNS-tunneled beacon that leaks sensitive environment details without user interaction.
AI Analysis
Technical Summary
The @sarex-team/sdk-js package at version 9.9.11 declares an install script that runs node index.js, which loads lib/core.js. This script gathers system information (os.userInfo().username, os.hostname(), process.cwd()) and combines it with a package tag and timestamp. It then performs DNS resolution requests to a subdomain of oob.sl4x0.xyz, an attacker-controlled domain, effectively creating a DNS-tunneled beacon. The domain and Node.js API names are stored as hex-encoded byte arrays in separate library files and decoded at runtime to evade detection. The beacon triggers automatically on npm install and on every require() call of the package, requiring no user interaction.
Potential Impact
This malicious package leaks sensitive system information to an attacker-controlled domain without user consent. The data exposed includes username, hostname, and current working directory, which can aid attackers in profiling the victim environment for further attacks or reconnaissance. The automatic execution on install and require() increases the risk of widespread data leakage in environments where this package is used.
Mitigation Recommendations
No official patch or remediation guidance is provided in the available data. Users should immediately remove and avoid using version 9.9.11 of @sarex-team/sdk-js. Verify dependencies and lockfiles to ensure this malicious version is not included. Monitor for updates or advisories from the package maintainers or npm registry regarding this issue. Consider using tools to detect malicious packages and audit dependencies regularly.
Malicious code in @sarex-team/sdk-js (npm)
Description
The npm package @sarex-team/sdk-js version 9.9.11 contains malicious code that executes automatically upon installation and usage. It collects system information such as username, hostname, and current working directory, then sends this data via DNS requests to an attacker-controlled domain. The malicious behavior is obfuscated by storing key strings as hex byte arrays and reconstructing them at runtime. This results in a DNS-tunneled beacon that leaks sensitive environment details without user interaction.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The @sarex-team/sdk-js package at version 9.9.11 declares an install script that runs node index.js, which loads lib/core.js. This script gathers system information (os.userInfo().username, os.hostname(), process.cwd()) and combines it with a package tag and timestamp. It then performs DNS resolution requests to a subdomain of oob.sl4x0.xyz, an attacker-controlled domain, effectively creating a DNS-tunneled beacon. The domain and Node.js API names are stored as hex-encoded byte arrays in separate library files and decoded at runtime to evade detection. The beacon triggers automatically on npm install and on every require() call of the package, requiring no user interaction.
Potential Impact
This malicious package leaks sensitive system information to an attacker-controlled domain without user consent. The data exposed includes username, hostname, and current working directory, which can aid attackers in profiling the victim environment for further attacks or reconnaissance. The automatic execution on install and require() increases the risk of widespread data leakage in environments where this package is used.
Mitigation Recommendations
No official patch or remediation guidance is provided in the available data. Users should immediately remove and avoid using version 9.9.11 of @sarex-team/sdk-js. Verify dependencies and lockfiles to ensure this malicious version is not included. Monitor for updates or advisories from the package maintainers or npm registry regarding this issue. Consider using tools to detect malicious packages and audit dependencies regularly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-14204
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a85b4c7acd9273b49252867
Added to database: 08/19/2026, 13:51:03 UTC
Last enriched: 08/19/2026, 14:41:22 UTC
Last updated: 08/19/2026, 14:41:22 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.