registry / Remote code execution / bigops-utils
bigops-utils
utility functions
This report shows the evidence for bigops-utils@35.4.8. 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, undisclosed import-time remote payload execution, not telemetry aligned with a small utility package. The absence of lifecycle scripts does not mitigate the reachable malicious entrypoint.
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-utils through index.js.
Impact
Arbitrary attacker-controlled native code can execute under the importing process account.
Mechanism
obfuscated remote binary download, temp-file drop, and detached execution
Attack narrative
A normal import invokes _helpers.js. Unless opt-out variables or a temporary cooldown file intervene, it selects an OS-specific endpoint, downloads a payload from rotating Workers hosts, or reconstructs one from DNS TXT records. It writes the resulting bytes to a randomized temp filename, marks it executable on Unix, and starts it detached through /bin/sh or cmd.exe, leaving the downloaded program to run independently.
AI rationale
This is concrete, undisclosed import-time remote payload execution, not telemetry aligned with a small utility package. The absence of lifecycle scripts does not mitigate the reachable malicious entrypoint.
Evidence
package.jsonindex.js_helpers.jsREADME.md
Network endpoints8
oob-worker.cf102-baf.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf103-070.workers.devoob-worker.cf99-9b3.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.dl.wel1.runet.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 _helpers.js on every package import.
- _helpers.js downloads platform-specific binary payloads over HTTPS or DNS TXT.
- _helpers.js writes payloads to temp storage, chmods Unix payloads, and launches them detached via shell/cmd.
- Remote hosts are obfuscated through string concatenation and rotated randomly.
- The generic utilities README does not disclose this import-time binary execution.
Evidence against
- package.json has no lifecycle scripts.
- No AI-agent configuration or credential-harvesting code was confirmed.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_helpers.jsView file
4const crypto = require("crypto");
L5: const https = require("https");
L6: const path = require("path");
...
L46: const COOLDOWN = 19908;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
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");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_helpers.jsView on unpkg · L44Trigger-reachable chain: manifest.main -> index.js -> _helpers.js
L4: const crypto = require("crypto");
L5: const https = require("https");
L6: const path = require("path");
...
L46: const COOLDOWN = 19908;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
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");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: 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 · L4Findings
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-utils@35.4.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-utils@35.4.8. 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.