Malicious code in tms-x-headers (npm)
The npm package tms-x-headers version 20.2.9 contains malicious code that, upon requiring the package, fetches a platform-specific binary from attacker-controlled hosts. This binary is saved to a temporary file with a name mimicking legitimate .NET diagnostic tools, made executable, and then executed without any signature verification. The code uses obfuscation techniques to evade detection, including fragmented hostnames and split strings for requiring modules. Installing or loading this package results in execution of attacker-controlled native code on the host system.
AI Analysis
Technical Summary
The tms-x-headers npm package version 20.2.9 includes malicious functionality in its _helpers.js file that dynamically downloads a platform-specific executable from fragmented and obfuscated external hosts not affiliated with the package publisher. The downloaded binary is saved to a temporary file with a plausible name (e.g., dotnet_diag_<hex>.exe on Windows) and executed detached via system shell commands without any integrity or signature checks. The package also loads the Node.js child_process module via split strings to evade static detection. This behavior leads to arbitrary native code execution on the host machine when the package is installed or required.
Potential Impact
This malicious package enables remote attacker-controlled native code execution on the host system of any user who installs or requires version 20.2.9 of tms-x-headers. The execution occurs without user consent or verification, potentially allowing full compromise of the affected system. The obfuscation and use of legitimate-looking filenames increase the risk of unnoticed exploitation.
Mitigation Recommendations
No official patch or remediation is currently documented for this malicious package version. Users should immediately avoid installing or using tms-x-headers version 20.2.9. Existing installations should be removed and replaced with trusted alternatives. Monitor package sources carefully and verify package integrity before installation. Since this is a malicious package, the best mitigation is to avoid its use entirely.
Malicious code in tms-x-headers (npm)
Description
The npm package tms-x-headers version 20.2.9 contains malicious code that, upon requiring the package, fetches a platform-specific binary from attacker-controlled hosts. This binary is saved to a temporary file with a name mimicking legitimate .NET diagnostic tools, made executable, and then executed without any signature verification. The code uses obfuscation techniques to evade detection, including fragmented hostnames and split strings for requiring modules. Installing or loading this package results in execution of attacker-controlled native code on the host system.
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 tms-x-headers npm package version 20.2.9 includes malicious functionality in its _helpers.js file that dynamically downloads a platform-specific executable from fragmented and obfuscated external hosts not affiliated with the package publisher. The downloaded binary is saved to a temporary file with a plausible name (e.g., dotnet_diag_<hex>.exe on Windows) and executed detached via system shell commands without any integrity or signature checks. The package also loads the Node.js child_process module via split strings to evade static detection. This behavior leads to arbitrary native code execution on the host machine when the package is installed or required.
Potential Impact
This malicious package enables remote attacker-controlled native code execution on the host system of any user who installs or requires version 20.2.9 of tms-x-headers. The execution occurs without user consent or verification, potentially allowing full compromise of the affected system. The obfuscation and use of legitimate-looking filenames increase the risk of unnoticed exploitation.
Defensive Guidance
No official patch or remediation is currently documented for this malicious package version. Users should immediately avoid installing or using tms-x-headers version 20.2.9. Existing installations should be removed and replaced with trusted alternatives. Monitor package sources carefully and verify package integrity before installation. Since this is a malicious package, the best mitigation is to avoid its use entirely.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12480
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a735746bf8831d53915a02d
Added to database: 08/05/2026, 15:31:18 UTC
Last enriched: 08/05/2026, 17:31:39 UTC
Last updated: 08/05/2026, 17:31:39 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.