registry / Remote code execution / lifestyle-test-utils
lifestyle-test-utils
common helpers
This report shows the evidence for lifestyle-test-utils@20.7.2, the only known version.
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-aiThe payload chain is reachable from the declared main entrypoint and enables arbitrary remote code execution without user action. Absence of lifecycle scripts does not mitigate import-time execution.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any require/import resolving main index.js.
Impact
Arbitrary native code execution under the importing process user.
Mechanism
download, drop, chmod, and detached-execute remote payload
Attack narrative
The main entrypoint silently requires _ext.js. On import, it records a temporary stamp, downloads a platform-specific payload from rotating worker hosts or DNS TXT records, writes it to a temp location, marks it executable on Unix, and launches it detached through /bin/sh or cmd.exe.
AI rationale
The payload chain is reachable from the declared main entrypoint and enables arbitrary remote code execution without user action. Absence of lifecycle scripts does not mitigate import-time execution.
Evidence
package.jsonindex.js_ext.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf103-070.workers.devoob-worker.cf100-416.workers.devoob-worker.cf102-baf.workers.devtin.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 _ext.js on every package import.
- _ext.js downloads platform binaries from worker hosts or DNS TXT.
- _ext.js writes executable content to /var/tmp or Windows Temp.
- _ext.js chmods then detached-spawns the downloaded file via shell/cmd.
- Download and execution errors are silently suppressed.
Evidence against
- package.json has no lifecycle scripts.
- Exported helpers in index.js are benign, but import triggers _ext.js.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
3 flagged · loading source_ext.jsView file
4const fs = require("fs");
L5: const https = require("https");
L6: const crypto = require("crypto");
...
L40: const STAMP_TTL = 19882;
L41: const _l = (...a) => process.stderr.write("");
L42:
...
L53: const isWin = _p("platform") === "win32";
L54: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L55: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L88: try {
L89: require("dns").resolveTxt(d, (e, rr) => {
L90: if (e || !rr || !rr.length) return r("");
Critical
4Trigger-reachable chain: manifest.main -> index.js -> _ext.js
L4: const fs = require("fs");
L5: const https = require("https");
L6: const crypto = require("crypto");
...
L40: const STAMP_TTL = 19882;
L41: const _l = (...a) => process.stderr.write("");
L42:
...
L53: const isWin = _p("platform") === "win32";
L54: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L55: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L88: try {
L89: require("dns").resolveTxt(d, (e, rr) => {
L90: 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.
_ext.jsView on unpkg · L4115
Findings
2 Critical1 High3 Medium2 Low
CriticalDownload Execute_ext.js
CriticalTrigger Reachable Dangerous Capability_ext.js
HighChild Process_ext.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to lifestyle-test-utils@20.7.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing lifestyle-test-utils@20.7.2. 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.