registry / Remote code execution / bigops-notes
bigops-notes
Bigops notes SDK for internal consumers
This report shows the evidence for bigops-notes@35.8.7, 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-aiDirect source inspection confirms reachable import-time remote payload execution, not merely telemetry behavior. The dormant telemetry module contains a similar downloader, reinforcing intent.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of the package main entrypoint.
Impact
Arbitrary remote code executes with the importing process's privileges.
Mechanism
import-time remote binary download, temporary-file drop, and detached execution
Attack narrative
The main module suppresses errors while loading _bootstrap.js. That file contacts concealed remote hosts for a platform-specific binary, optionally reconstructs one from DNS TXT records, writes it into a temporary directory, changes Unix permissions, and launches it detached. This is an unconsented import-time staged remote-code-execution chain.
AI rationale
Direct source inspection confirms reachable import-time remote payload execution, not merely telemetry behavior. The dormant telemetry module contains a similar downloader, reinforcing intent.
Evidence
package.jsonindex.js_bootstrap.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf103-070.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf100-416.workers.devoob-worker.cf99-9b3.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.dl.wel1.ru
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _bootstrap.js on every package import.
- _bootstrap.js downloads platform binaries from obfuscated workers.dev hosts.
- It falls back to DNS TXT payload retrieval via dl.wel1.ru domains.
- Downloaded data is written to a temp file, made executable, and detached-spawned via shell/cmd.
- No lifecycle hook is needed: requiring the main entrypoint triggers the chain.
Evidence against
- package.json has no npm lifecycle scripts.
- The documented API is minimal, but it does not explain the import-time bootstrapper.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading source_bootstrap.jsView file
5const os = require("os");
L6: const https = require("https");
L7: const fs = require("fs");
...
L45: const TTL = 20308;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L59: const isWin = _p("platform") === "win32";
L60: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L61: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L94: try {
L95: require("dns").resolveTxt(d, (e, rr) => {
L96: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_bootstrap.jsView on unpkg · L55Trigger-reachable chain: manifest.main -> index.js -> _bootstrap.js
L5: const os = require("os");
L6: const https = require("https");
L7: const fs = require("fs");
...
L45: const TTL = 20308;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L59: const isWin = _p("platform") === "win32";
L60: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L61: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L94: try {
L95: require("dns").resolveTxt(d, (e, rr) => {
L96: 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.
_bootstrap.jsView on unpkg · L5Findings
2 Critical2 High3 Medium2 Low
CriticalDownload Execute_bootstrap.js
CriticalTrigger Reachable Dangerous Capability_bootstrap.js
HighChild Process_bootstrap.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to bigops-notes@35.8.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-notes@35.8.7. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.