Malicious code in bigops-products-investment (npm)
Published Sources: OSV
What is affected, what to do
The available sources name no fixed version. Check the vendor guidance in the references below.
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
—
Priority
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- Not rated
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 22.17 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (91a3c32ddd31a89386c67c18f6dcc9d80d621671986dbb9a059927dfcf749411)
Requiring bigops-products-investment@35.3.1 loads vendor.js at import time, which fetches a platform-specific executable from one of several Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev) whose hostnames are assembled via string-array.join concatenation to evade static detection. The downloaded bytes are written to /var/tmp or %TEMP% under disguised names (".cache" on POSIX, "dotnet_diag_.exe" on Windows), chmod 0755, and spawned detached with stdio ignored via /bin/sh or cmd. No hash or signature verification is performed. If the HTTPS fetch fails, the loader falls back to a covert DNS-TXT retrieval channel, querying chunked TXT records under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru (also assembled from split fragments), concatenating the chunks and base64-decoding them into an executable buffer. A separate 81KB lib/telemetry.js is bundled but not referenced from index.js. The package labels its state file "analytics_state" and gates opt-out on DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK, but the behavior is fetch-and-execute of author-controlled opaque binaries — not telemetry.