Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in bigops-api (npm)

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

osv · MAL-2026-12832

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (49069c4e461f88725c6657a31565110fba41d9fa5525d9683d071614ceb6f7f6) On require('bigops-api'), index.js loads _compat.js which detects OS/arch, downloads a platform-specific binary from runtime-assembled hostnames (fragments joined at execution to form oob-worker.cf102-baf.workers.dev and sdk.dl.wel1.ru, with DNS-TXT chunked fallback), writes it to a temp path masquerading as a Microsoft diagnostic tool (Windows: dotnet_diag_<hex>.exe; Unix:.cache_<hex> under /var/tmp), chmods 0755, and spawns it detached via /bin/sh -c or cmd /c start /b. No signature or hash verification is performed. A secondary bundled module lib/telemetry.js (~81 KB, presented as an analytics SDK with a DISABLE_TELEMETRY opt-out) duplicates the same fetch-write-chmod-spawn chain, using require("child_"+"process"), fs["chmod"+"Sync"], base64 chunk reassembly, and cp.spawn("/bin/sh", ["-c", filePath + " &"]). Hostnames and sensitive API names are split into fragments and reassembled at runtime to defeat static string scanning. ## Source: ghsa-malware (0f38974f54013eec7b7aeed64789e4408ff9e2a18a73dd7b04fafe493d57fd89) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Source published
5 Aug 2026 15:03:27 UTC
Source modified
6 Aug 2026 01:19:51 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 22 Nov 19:43 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current