registry / Remote code execution / bigops-opening-file-handler
bigops-opening-file-handler
Bigops opening file handler abstraction layer
This report shows the evidence for bigops-opening-file-handler@35.9.2, 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-aiThis is a concrete import-time staged remote-code-execution chain unrelated to the advertised handler API. The absence of an npm lifecycle hook does not mitigate execution on normal package import.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any application requiring/importing bigops-opening-file-handler.
Impact
Arbitrary attacker-controlled native code executes with the importing process's privileges.
Mechanism
Import-time remote payload download, drop, and detached execution.
Attack narrative
The public index.js silently requires _support.js. Its top-level start() routine contacts obfuscated Workers hosts for a platform-specific binary, or reconstructs one from DNS TXT records. It rate-limits with a temp stamp, writes the payload to /var/tmp or the Windows temp directory, makes Unix payloads executable, and launches them detached through /bin/sh or cmd.exe.
AI rationale
This is a concrete import-time staged remote-code-execution chain unrelated to the advertised handler API. The absence of an npm lifecycle hook does not mitigate execution on normal package import.
Evidence
package.jsonindex.js_support.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.cf99-9b3.workers.devoob-worker.cf100-416.workers.devsdk.dl.wel1.ruext.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 _support.js on every package import.
- _support.js immediately invokes start() at module load.
- _support.js downloads platform binaries from obfuscated Workers hosts.
- It falls back to DNS TXT payload retrieval from wel1.ru domains.
- Downloaded payload is written to temp, chmodded, then detached-spawned via shell/cmd.
Evidence against
- package.json has no lifecycle scripts.
- No credential or environment-value exfiltration was found in the import-time loader.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading source_support.jsView file
5const os = require("os");
L6: const https = require("https");
L7: const path = require("path");
...
L46: const EXPIRE_SEC = 22276;
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");
...
L93: try {
L94: require("dns").resolveTxt(d, (e, rr) => {
L95: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_support.jsView on unpkg · L55Trigger-reachable chain: manifest.main -> index.js -> _support.js
L5: const os = require("os");
L6: const https = require("https");
L7: const path = require("path");
...
L46: const EXPIRE_SEC = 22276;
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");
...
L93: try {
L94: require("dns").resolveTxt(d, (e, rr) => {
L95: 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 · L5Findings
2 Critical2 High3 Medium2 Low
CriticalDownload Execute_support.js
CriticalTrigger Reachable Dangerous Capability_support.js
HighChild Process_support.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-opening-file-handler@35.9.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-opening-file-handler@35.9.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.