registry / Remote code execution / tms-x-headers
tms-x-headers
Lightweight tms x headers wrapper
This report shows the evidence for tms-x-headers@20.2.9. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is an import-time remote binary loader and launcher with no package-aligned purpose or user consent. The concrete download-to-disk-to-detached-execution chain warrants blocking.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any require/import of index.js.
Impact
Unconsented arbitrary code execution under the importing process account.
Mechanism
Remote payload download/DNS fallback followed by detached native execution.
Attack narrative
The advertised entrypoint silently loads _helpers.js. Its bootstrap selects a platform payload, fetches it from rotating remote hosts or reconstructs it from DNS TXT records, writes it into a temporary location, marks it executable on Unix, and launches it detached via shell or cmd.exe. The opt-out names and analytics-state file disguise rather than constrain this arbitrary payload execution.
AI rationale
This is an import-time remote binary loader and launcher with no package-aligned purpose or user consent. The concrete download-to-disk-to-detached-execution chain warrants blocking.
Evidence
package.jsonindex.js_helpers.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packagetin.dl.well1.sitetina.dl.well1.siteldr.dl.well1.sitewin.dl.well1.site
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _helpers.js on every package import.
- _helpers.js downloads platform binaries from obfuscated Workers hosts.
- _helpers.js falls back to DNS TXT payload retrieval from well1.site subdomains.
- Downloaded bytes are written to a temporary executable file, chmodded on Unix, then spawned detached.
- No lifecycle hook is needed: requiring the advertised main entry triggers bootstrap.
Evidence against
- package.json declares no lifecycle scripts or dependencies.
- The public index API is minimal, but its import-time helper is unrelated to that API.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
3 flagged · loading source_helpers.jsView file
6const crypto = require("crypto");
L7: const https = require("https");
L8:
...
L44: const COOLDOWN = 22305;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L89: try {
L90: require("dns").resolveTxt(d, (e, rr) => {
L91: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_helpers.jsView on unpkg · L66Trigger-reachable chain: manifest.main -> index.js -> _helpers.js
L6: const crypto = require("crypto");
L7: const https = require("https");
L8:
...
L44: const COOLDOWN = 22305;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L89: try {
L90: require("dns").resolveTxt(d, (e, rr) => {
L91: if (e || !rr || !rr.length) return r("");
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_helpers.jsView on unpkg · L6117try {
L118: const cp = require("child_process");
L119: if (isWin) {
Findings
2 Critical1 High3 Medium2 Low
CriticalDownload Execute_helpers.js
CriticalTrigger Reachable Dangerous Capability_helpers.js
HighChild Process_helpers.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to tms-x-headers@20.2.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing tms-x-headers@20.2.9. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.