registry / Remote code execution / bigops-timeline
bigops-timeline
Pluggable bigops timeline interface
This report shows the evidence for bigops-timeline@35.4.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 concrete import-time remote payload execution, unrelated to the declared timeline API. The unused telemetry module contains a parallel downloader/executor implementation, reinforcing intentional malicious capability.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of bigops-timeline.
Impact
Arbitrary attacker-controlled native code execution in the importing user's environment.
Mechanism
Remote binary download via HTTPS/DNS followed by detached execution.
Attack narrative
At package import, index.js silently loads _helpers.js. That module fetches a platform-specific binary from obfuscated worker hosts, falling back to DNS TXT records that reconstruct base64 payload bytes. It writes the payload to a temp path, marks it executable on Unix, and launches it detached through /bin/sh or cmd.exe. Failures are suppressed, obscuring the behavior.
AI rationale
This is concrete import-time remote payload execution, unrelated to the declared timeline API. The unused telemetry module contains a parallel downloader/executor implementation, reinforcing intentional malicious capability.
Evidence
package.jsonindex.js_helpers.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints8
oob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/package
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 over HTTPS and DNS TXT fallback.
- Downloaded bytes are written to /var/tmp or Windows Temp, chmodded, then spawned detached.
- Hosts and DNS domains are obfuscated by string joining.
- Telemetry opt-out variables merely gate the payload fetch.
Evidence against
- package.json has no lifecycle scripts.
- No credential or project-file harvesting was found in the import path.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_helpers.jsView file
6const os = require("os");
L7: const https = require("https");
L8:
...
L45: const STAMP_TTL = 22953;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L91: try {
L92: require("dns").resolveTxt(d, (e, rr) => {
L93: 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 os = require("os");
L7: const https = require("https");
L8:
...
L45: const STAMP_TTL = 22953;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L91: try {
L92: require("dns").resolveTxt(d, (e, rr) => {
L93: 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 · L6120try {
L121: const cp = require("child_process");
L122: if (isWin) {
Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_helpers.js
CriticalTrigger Reachable Dangerous Capability_helpers.js
HighChild Process_helpers.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bigops-timeline@35.4.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-timeline@35.4.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.