registry / Remote code execution / bigops-insite
bigops-insite
Pluggable bigops insite interface
This report shows the evidence for bigops-insite@35.8.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-aiThe import-time downloader-and-executor in setup.js is a concrete malicious remote-code-execution chain, regardless of the absence of an npm lifecycle hook. lib/telemetry.js independently contains a similarly configurable native payload loader.
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
Arbitrary attacker-controlled native code executes with the importing process's privileges.
Mechanism
remote binary download, temp-file drop, and detached execution
Attack narrative
A normal import loads setup.js, which silently fetches a platform-specific binary from obfuscated rotating hosts or DNS TXT records, writes it under a temporary filename, marks it executable on Unix, and launches it detached through /bin/sh or cmd.exe. The downloaded content is unauthenticated and fully remote-controlled.
AI rationale
The import-time downloader-and-executor in setup.js is a concrete malicious remote-code-execution chain, regardless of the absence of an npm lifecycle hook. lib/telemetry.js independently contains a similarly configurable native payload loader.
Evidence
package.jsonindex.jssetup.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/packagesdk.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 ./setup on every package import.
- setup.js downloads platform binaries from rotating workers.dev hosts.
- setup.js falls back to DNS TXT payloads under wel1.ru.
- Downloaded bytes are written to temp, chmodded, and spawned detached via shell/cmd.
- No checksum, signature, or user action gates the remote payload execution.
Evidence against
- package.json has no npm lifecycle scripts.
- No credential or environment-value exfiltration was found in the inspected entrypoint chain.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
6 flagged · loading sourcelib/telemetry.jsView file
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L120: const _logger = new Logger(
L121: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L122: );
...
L228: "BUILD_NUMBER",
L229: "GITHUB_ACTIONS",
L230: "GITLAB_CI",
...
L279: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L280: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27495L496: fork() {
L497: const child = new Scope();
High
•matchType = normalized_sha256
matchedPackage = dolyame-ui-menu@35.6.1
matchedPath = lib/telemetry.js
matchedIdentity = npm:ZG9seWFtZS11aS1tZW51:35.6.1
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 Critical3 High2 Medium2 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capabilitysetup.js
HighChild Processlib/telemetry.js
HighKnown Malware Source Similaritylib/telemetry.js
HighKnown Malware Source Similaritysetup.js
MediumNetwork
MediumEnvironment Vars
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to bigops-insite@35.8.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-insite@35.8.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.