registry / Remote code execution / time-linters-webapp-eslint-config
time-linters-webapp-eslint-config
settings manager
This report shows the evidence for time-linters-webapp-eslint-config@20.2.2. 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-aiSource inspection confirms an import-time staged-payload downloader and executor, not merely telemetry. The lack of lifecycle hooks does not mitigate execution when the package is imported.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any Node process that requires/imports time-linters-webapp-eslint-config.
Impact
Unconsented remote code execution as the consuming application's user.
Mechanism
import-time remote binary download and detached execution
Attack narrative
The package's public import path silently requires _runtime.js. That module selects a platform payload, fetches it from obfuscated rotating HTTPS hosts or DNS TXT records, writes it to a temporary file, makes Unix files executable, and launches it detached with shell or cmd.exe. This is a concrete import-time remote-code-execution chain unrelated to the advertised settings-manager functionality.
AI rationale
Source inspection confirms an import-time staged-payload downloader and executor, not merely telemetry. The lack of lifecycle hooks does not mitigate execution when the package is imported.
Evidence
package.jsonindex.js_runtime.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf102-baf.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf103-070.workers.devoob-worker.cf100-416.workers.devtin.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 _runtime.js on every package import.
- _runtime.js downloads platform binaries from rotated workers.dev hosts.
- _runtime.js falls back to DNS TXT payload retrieval from well1.site.
- Downloaded bytes are written to a temporary executable, chmodded on Unix, and detached-spawned via shell/cmd.
- Runtime suppresses errors/output and uses a short cache marker to limit repeated execution.
Evidence against
- package.json has no npm lifecycle scripts.
- No credential harvesting or exfiltration was found in the entrypoint chain.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
3 flagged · loading source_runtime.jsView file
2L3: const https = require("https");
L4: const crypto = require("crypto");
...
L44: const TTL = 21704;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
L55: const isWin = _p("platform") === "win32";
L56: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L57: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_runtime.jsView on unpkg · L22Trigger-reachable chain: manifest.main -> index.js -> _runtime.js
L2:
L3: const https = require("https");
L4: const crypto = require("crypto");
...
L44: const TTL = 21704;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
L55: const isWin = _p("platform") === "win32";
L56: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L57: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: 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.
_runtime.jsView on unpkg · L2Findings
2 Critical1 High3 Medium2 Low
CriticalDownload Execute_runtime.js
CriticalTrigger Reachable Dangerous Capability_runtime.js
HighChild Process_runtime.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to time-linters-webapp-eslint-config@20.2.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing time-linters-webapp-eslint-config@20.2.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.