registry / Remote code execution / bigops-shared-ui
bigops-shared-ui
visual components
This report shows the evidence for bigops-shared-ui@35.1.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-aiSource inspection confirms a reachable import-time remote payload download-and-execute chain. The absence of lifecycle hooks does not mitigate execution when consumers import the package.
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-shared-ui, including normal application startup.
Impact
Arbitrary remote code executes with the privileges of the importing Node.js process.
Mechanism
import-time remote binary download, DNS fallback, and detached execution
Attack narrative
The package's main entrypoint silently loads setup.js. On import, setup.js fetches a platform-specific payload from obfuscated remote hosts or reconstructs one through DNS TXT records, saves it under a disguised temporary filename, changes Unix permissions, and starts it detached through a shell. This is an unconsented remote-code-execution chain unrelated to the stated UI functionality.
AI rationale
Source inspection confirms a reachable import-time remote payload download-and-execute chain. The absence of lifecycle hooks does not mitigate execution when consumers import the package.
Evidence
package.jsonindex.jssetup.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>TEMP/analytics_stateTEMP/dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf102-baf.workers.devoob-worker.cf99-9b3.workers.devoob-worker.cf103-070.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 ./setup on every package import.
- setup.js downloads platform-specific binaries over HTTPS.
- setup.js reconstructs binary payloads from DNS TXT records.
- Downloaded bytes are written to /var/tmp or TEMP and made executable.
- setup.js launches the payload via /bin/sh or cmd.exe detached.
- Endpoints are obfuscated workers.dev hosts and dl.wel1.ru domains.
Evidence against
- package.json has no npm lifecycle scripts.
- README describes only a UI package, not a native profiler or downloader.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
5 flagged · loading sourcelib/telemetry.jsView file
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L116: const _logger = new Logger(
L117: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L118: );
...
L224: "BUILD_NUMBER",
L225: "GITHUB_ACTIONS",
L226: "GITLAB_CI",
...
L275: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L276: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27491L492: fork() {
L493: const child = new Scope();
High
•matchType = normalized_sha256
matchedPackage = devplatform-hooks@35.2.1
matchedPath = lib/telemetry.js
matchedIdentity = npm:ZGV2cGxhdGZvcm0taG9va3M:35.2.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 Critical2 High2 Medium2 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capabilitysetup.js
HighChild Processlib/telemetry.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to bigops-shared-ui@35.1.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-shared-ui@35.1.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.