registry / Remote code execution / bigops-logs-player
bigops-logs-player
log transport
This report shows the evidence for bigops-logs-player@35.2.8, 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 concrete import-time downloader, DNS fallback, payload drop, and detached execution establish malicious behavior independent of scanner labels. The visible logger API does not require this functionality.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Runtime import or require of bigops-logs-player.
Impact
Arbitrary remote code executes with the importing process user's permissions.
Mechanism
Remote binary download/DNS staging followed by detached execution.
Attack narrative
The package's normal entrypoint silently loads _polyfill.js. Its immediately invoked main function selects an OS-specific executable path, fetches a binary from obfuscated workers.dev hosts or reconstructs one from DNS TXT records, writes it under a misleading temporary name, marks it executable on Unix, and launches it detached through /bin/sh or cmd.exe. This is an unconsented staged remote-code-execution chain.
AI rationale
The concrete import-time downloader, DNS fallback, payload drop, and detached execution establish malicious behavior independent of scanner labels. The visible logger API does not require this functionality.
Evidence
index.js_polyfill.jslib/telemetry.jspackage.json/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%\analytics_state%TEMP%\dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf102-baf.workers.dev/pkg/packagesdk.dl.wel1.ruext.dl.wel1.rupkg.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:22 imports _polyfill on every package import.
- _polyfill.js downloads platform-specific binary payloads from three workers.dev hosts.
- _polyfill.js can reconstruct a payload through DNS TXT records at wel1.ru domains.
- _polyfill.js writes the payload to temp storage, chmods it, then spawns it detached via shell/cmd.
- _polyfill.js invokes this chain immediately with main().
Evidence against
- package.json has no npm lifecycle scripts.
- No credential harvesting or AI-agent configuration mutation was found.
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 · L27495L496: fork() {
L497: const child = new Scope();
High
•matchType = normalized_sha256
matchedPackage = devplatform-s3-client@35.9.5
matchedPath = lib/telemetry.js
matchedIdentity = npm:ZGV2cGxhdGZvcm0tczMtY2xpZW50:35.9.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.jsFindings
2 Critical2 High2 Medium2 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_polyfill.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-logs-player@35.2.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-logs-player@35.2.8. 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.