registry / Remote code execution / bigops-statements-timeline

bigops-statements-timeline

Bigops statements timeline abstraction layer

This report shows the evidence for bigops-statements-timeline@35.2.4. 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-ai

The package’s normal import path performs stealthy remote payload retrieval and execution, with no user action or documented need. Obfuscated endpoint construction, DNS fallback, temporary binary names, and suppressed errors reinforce malicious intent.

Static reason

High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review

Trigger

Runtime require/import of bigops-statements-timeline.

Impact

Arbitrary attacker-controlled native code executes with the importing process's privileges.

Mechanism

remote binary download, drop, chmod, and detached execution

Attack narrative

Requiring index.js loads _support.js and immediately calls run(). It contacts rotated workers.dev hosts for a platform-specific payload, with DNS TXT reconstruction from wel1.ru as fallback. A payload over 1000 bytes is dropped in a temporary directory, chmodded on Unix, and launched through a detached shell or cmd.exe process. This is concrete remote code execution hidden behind an unrelated state-store package.

AI rationale

Evidence

package.jsonindex.js_support.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%\analytics_state%TEMP%\dotnet_diag_<random>.exe

Network endpoints8

oob-worker.cf99-9b3.workers.devoob-worker.cf103-070.workers.devoob-worker.cf102-baf.workers.dev

Decision evidence

public snapshot

AI called this Malicious at 99.0% confidence as Malware with low false-positive risk.

Evidence for block

index.js imports _support.js on every package import.
_support.js downloads platform binaries from four workers.dev hosts.
_support.js falls back to DNS TXT payload retrieval from *.wel1.ru.
Downloaded bytes are written to /var/tmp or TEMP, made executable, and spawned detached.
No lifecycle hook is needed: runtime import triggers run() automatically.

Evidence against

package.json contains no lifecycle scripts.
No credential harvesting or data exfiltration was confirmed.

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetwork

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 84.7 KB of source

Source & flagged code

4 flagged

_support.jsView file

2L3: const https = require("https"); L4: const crypto = require("crypto"); ... L43: const STAMP_TTL = 22434; L44: const _l = (...a) => process.stderr.write(""); L45: ... 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"); ... L87: try { L88: require("dns").resolveTxt(d, (e, rr) => { L89: if (e || !rr || !rr.length) return r("");

Critical

Download Execute

Source downloads or fetches remote code and executes it.

_support.jsView on unpkg · L2

2Trigger-reachable chain: manifest.main -> index.js -> _support.js L2: L3: const https = require("https"); L4: const crypto = require("crypto"); ... L43: const STAMP_TTL = 22434; L44: const _l = (...a) => process.stderr.write(""); L45: ... 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"); ... L87: try { L88: require("dns").resolveTxt(d, (e, rr) => { L89: 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.

_support.jsView on unpkg · L2

116try { L117: const cp = require("child_process"); L118: if (isWin) {

High

Child Process

Package source references child process execution.

_support.jsView on unpkg · L116

lib/telemetry.jsView file

•matchType = normalized_sha256 matchedPackage = devplatform-po-declaration-generator@35.2.7 matchedPath = lib/telemetry.js matchedIdentity = npm:[redacted]:35.2.7 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

lib/telemetry.jsView on unpkg

Source & flagged code

4 flagged · loading source

_support.jsView file

Critical

Download Execute

Source downloads or fetches remote code and executes it.

_support.jsView on unpkg · L2

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

_support.jsView on unpkg · L2

Findings

2 Critical2 High2 Medium1 Low

CriticalDownload Execute_support.js

CriticalTrigger Reachable Dangerous Capability_support.js

HighChild Process_support.js

HighKnown Malware Source Similaritylib/telemetry.js

MediumNetwork

MediumEnvironment Vars

LowFilesystem

Affected versions and remediation

This report applies to bigops-statements-timeline@35.2.4.

The versions list below shows the verdict for each recorded version.

Avoid installing bigops-statements-timeline@35.2.4. 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: 2026-08-26 01:18:20.404Z (UTC).

Source advisory published: 2026-08-05 15:34:01.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

2 known versions

0.0.1-securitylatestClean—AllowPublishedAug 25, 2026, 3:48 PM 35.2.4shownMaliciousRemote Code ExecutionBlockPublishedAug 5, 2026, 2:04 PM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other remote code execution packages

Source & flagged code

Related packages

Other remote code execution packages