registry / Remote code execution / bigops-nitro-client
bigops-nitro-client
Pluggable bigops nitro client interface
This report shows the evidence for bigops-nitro-client@35.6.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 payload execution unrelated to the advertised client abstraction. Opt-out environment checks and lack of an npm lifecycle hook do not mitigate the runtime compromise.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of index.js.
Impact
Untrusted remote code executes with the privileges of the importing Node process.
Mechanism
remote binary download, drop, chmod, and detached execution
Attack narrative
Requiring index.js silently imports _vendor.js. Its bootstrap routine downloads an unsigned binary from rotating workers.dev hosts, or reconstructs one from DNS TXT records, then writes it to a temporary hidden/random path, makes it executable on Unix, and launches it detached through /bin/sh or cmd.exe. The marker file and suppressed errors make execution quiet and rate-limited.
AI rationale
This is concrete import-time remote payload execution unrelated to the advertised client abstraction. Opt-out environment checks and lack of an npm lifecycle hook do not mitigate the runtime compromise.
Evidence
package.jsonindex.js_vendor.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.cf100-416.workers.devoob-worker.cf102-baf.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 _vendor automatically on package import.
- _vendor.js downloads platform binaries from worker hosts or DNS TXT.
- _vendor.js writes a hidden temp binary, chmods it, and starts it detached via shell/cmd.
- The payload has no signature or integrity verification.
- A temp marker throttles repeated execution and errors are suppressed.
Evidence against
- package.json contains no lifecycle scripts.
- No concrete credential-harvesting code was found in the import path.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_vendor.jsView file
3const os = require("os");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L45: const MAX_AGE = 20913;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_vendor.jsView on unpkg · L33Trigger-reachable chain: manifest.main -> index.js -> _vendor.js
L3: const os = require("os");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L45: const MAX_AGE = 20913;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: 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.
_vendor.jsView on unpkg · L3118try {
L119: const cp = require("child_process");
L120: if (isWin) {
High
lib/telemetry.jsView file
•matchType = normalized_sha256
matchedPackage = bigops-products-accounts-and-cards@35.7.5
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:35.7.5
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/telemetry.jsView on unpkgFindings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_vendor.js
CriticalTrigger Reachable Dangerous Capability_vendor.js
HighChild Process_vendor.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bigops-nitro-client@35.6.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-nitro-client@35.6.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.