Malicious code in twork-data-services-getting-arrests (npm)
Published Sources: OSV
What is affected, what to do
twork-data-services-getting-arrests@20.1.1 acts as a binary dropper. index.js top-level requires./_support.js, whose start() runs at load time: it selects a platform-specific endpoint, downloads a payload from one of several Cloudflare Workers hosts whose hostnames are assembled at runtime by string fragment concatenation (e.g. ["oob-w","orker.cf","99-9b3",".workers.d","ev"].join("")) with a DNS TXT fallback under *.dl.well1.site, writes it to /tmp or %TEMP% under a disguised filename (.cache_<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmods 0755, and detach-spawns it via /bin/sh -c '<file> &' or cmd.exe /c start. The content is not hash- or signature-verified, the destination hosts are anonymous and mutable, and the filename mimics legitimate cache/diagnostic artifacts.
The available sources name no fixed version. Check the vendor guidance and the linked original advisory.
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
—
XIEM Effective CVSS
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- 21.30 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
twork-data-services-getting-arrests@20.1.1 acts as a binary dropper. index.js top-level requires./_support.js, whose start() runs at load time: it selects a platform-specific endpoint, downloads a payload from one of several Cloudflare Workers hosts whose hostnames are assembled at runtime by string fragment concatenation (e.g. ["oob-w","orker.cf","99-9b3",".workers.d","ev"].join("")) with a DNS TXT fallback under *.dl.well1.site, writes it to /tmp or %TEMP% under a disguised filename (.cache_<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmods 0755, and detach-spawns it via /bin/sh -c '<file> &' or cmd.exe /c start. The content is not hash- or signature-verified, the destination hosts are anonymous and mutable, and the filename mimics legitimate cache/diagnostic artifacts. A second, more heavily obfuscated copy of the same dropper is bundled at lib/telemetry.js under cover-story class names (Logger, HttpTransport, ServiceDiscovery, WorkerHost) using the same primitives (Buffer.from(chunks,'base64'), cp.spawn('/bin/sh', ['-c', filePath + ' &']), fs['chmod'+'Sync'], require('child_'+'process')). Any consumer that installs and requires this package executes attacker-controlled native code with the user's privileges on the host. 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.