registry / Remote code execution / bigops-products-deposits
bigops-products-deposits
Bigops products deposits runtime support module
This report shows the evidence for bigops-products-deposits@35.9.1, 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 concrete import-time remote code execution, not package-aligned telemetry: the payload is opaque, unverified, concealed behind obfuscated domains, and launched detached.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any Node.js require/import of the package entrypoint.
Impact
Arbitrary attacker-controlled code executes with the importing process's privileges.
Mechanism
remote binary download, temporary-file drop, chmod, and detached execution
Attack narrative
The public entrypoint suppresses errors while importing _runtime.js. At import time it downloads a platform-specific payload from rotated Workers hosts, falling back to DNS TXT data from wel1.ru domains. It writes the unverified bytes into a temporary executable file, makes Unix payloads executable, and launches them detached through /bin/sh or cmd.exe. The same remote-payload pattern is also embedded in lib/telemetry.js.
AI rationale
This is concrete import-time remote code execution, not package-aligned telemetry: the payload is opaque, unverified, concealed behind obfuscated domains, and launched detached.
Evidence
package.jsonindex.js_runtime.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.cf101-adf.workers.devoob-worker.cf100-416.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf99-9b3.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 _runtime.js on every package import.
- _runtime.js downloads platform binaries over HTTPS and DNS TXT.
- Downloaded bytes are written to /var/tmp or Windows Temp, chmodded, then launched detached.
- Remote hosts are obfuscated and rotated; no integrity/signature verification exists.
- A temporary rate-limit stamp masks repeated execution.
Evidence against
- package.json contains no lifecycle hook.
- README documents only a normal require API.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
5 flagged · loading source_runtime.jsView file
3const fs = require("fs");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L46: const CACHE_TTL = 21787;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
L57: const isWin = _p("platform") === "win32";
L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L59: 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.
_runtime.jsView on unpkg · L33Trigger-reachable chain: manifest.main -> index.js -> _runtime.js
L3: const fs = require("fs");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L46: const CACHE_TTL = 21787;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
L57: const isWin = _p("platform") === "win32";
L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L59: 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.
_runtime.jsView on unpkg · L3Findings
2 Critical3 High2 Medium1 Low
CriticalDownload Execute_runtime.js
CriticalTrigger Reachable Dangerous Capability_runtime.js
HighChild Process_runtime.js
HighKnown Malware Source Similaritylib/telemetry.js
HighKnown Malware Source Similarity_runtime.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bigops-products-deposits@35.9.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-products-deposits@35.9.1. 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.