Malicious code in statist-statist-core (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (192fac66540fb5d3f4c376673ddd67a4e43053342e745e538f7ddcc08b0a9042) index.js requires./setup on module load. setup.js assembles obfuscated destination hostnames from split string arrays, selects a platform-specific endpoint from four hardcoded Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), downloads an opaque binary via https.get, writes it to /tmp or %TEMP% under a disguised name (dotnet_diag_<suffix>.exe on Windows,.cache_<suffix> on Unix), chmods 0755, and spawns it detached via spawn("/bin/sh") or spawn("cmd"). When HTTPS fetch fails, setup.js falls back to a DNS TXT-record channel under *.dl.well1.site (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site): it queries a count record and then N chunk records, base64-decodes the concatenation, and executes the reconstructed payload — an evasion channel that bypasses HTTP egress filtering. The child_process module name and destination hostnames are runtime-assembled from split arrays to defeat static scanners; disguised filenames and an analytics/telemetry framing serve as cover. The fetch-and-execute path fires automatically whenever any consumer requires this package. ## Source: ghsa-malware (951066f8fd3f0cc78122046780b65659e2e22d1aa548afaeb26b8a8ca5bad739) 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.
AI Analysis
Technical Summary
The statist-statist-core package (npm) version 20.9.9 includes a malicious module that, upon loading, assembles obfuscated destination hostnames and downloads an opaque binary payload from one of four hardcoded Cloudflare Workers hosts. The binary is saved to temporary directories with disguised filenames and executed detached via shell commands. If the HTTPS fetch fails, the malware falls back to a DNS TXT record exfiltration channel to retrieve and execute the payload, bypassing HTTP egress filtering. The code uses runtime assembly of module names and hostnames to evade static scanners and disguises its activity with analytics/telemetry framing. This malicious fetch-and-execute sequence activates automatically whenever the package is imported.
Potential Impact
This malicious package can lead to arbitrary code execution on the host system, potentially allowing attackers to run unauthorized binaries with the privileges of the user running the Node.js process. The use of obfuscation, fallback DNS channels, and disguised filenames increases the difficulty of detection and containment. There is no indication of active exploitation in the wild at this time.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should immediately cease using version 20.9.9 of statist-statist-core. Remove the package from all environments and replace it with a trusted alternative. Monitor for any unexpected processes or binaries matching the described patterns. Since no vendor advisory or patch is available, patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates. Avoid using this package until a clean, verified version is released.
Malicious code in statist-statist-core (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (192fac66540fb5d3f4c376673ddd67a4e43053342e745e538f7ddcc08b0a9042) index.js requires./setup on module load. setup.js assembles obfuscated destination hostnames from split string arrays, selects a platform-specific endpoint from four hardcoded Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), downloads an opaque binary via https.get, writes it to /tmp or %TEMP% under a disguised name (dotnet_diag_<suffix>.exe on Windows,.cache_<suffix> on Unix), chmods 0755, and spawns it detached via spawn("/bin/sh") or spawn("cmd"). When HTTPS fetch fails, setup.js falls back to a DNS TXT-record channel under *.dl.well1.site (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site): it queries a count record and then N chunk records, base64-decodes the concatenation, and executes the reconstructed payload — an evasion channel that bypasses HTTP egress filtering. The child_process module name and destination hostnames are runtime-assembled from split arrays to defeat static scanners; disguised filenames and an analytics/telemetry framing serve as cover. The fetch-and-execute path fires automatically whenever any consumer requires this package. ## Source: ghsa-malware (951066f8fd3f0cc78122046780b65659e2e22d1aa548afaeb26b8a8ca5bad739) 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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The statist-statist-core package (npm) version 20.9.9 includes a malicious module that, upon loading, assembles obfuscated destination hostnames and downloads an opaque binary payload from one of four hardcoded Cloudflare Workers hosts. The binary is saved to temporary directories with disguised filenames and executed detached via shell commands. If the HTTPS fetch fails, the malware falls back to a DNS TXT record exfiltration channel to retrieve and execute the payload, bypassing HTTP egress filtering. The code uses runtime assembly of module names and hostnames to evade static scanners and disguises its activity with analytics/telemetry framing. This malicious fetch-and-execute sequence activates automatically whenever the package is imported.
Potential Impact
This malicious package can lead to arbitrary code execution on the host system, potentially allowing attackers to run unauthorized binaries with the privileges of the user running the Node.js process. The use of obfuscation, fallback DNS channels, and disguised filenames increases the difficulty of detection and containment. There is no indication of active exploitation in the wild at this time.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should immediately cease using version 20.9.9 of statist-statist-core. Remove the package from all environments and replace it with a trusted alternative. Monitor for any unexpected processes or binaries matching the described patterns. Since no vendor advisory or patch is available, patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates. Avoid using this package until a clean, verified version is released.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12456
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a735747bf8831d53915a09a
Added to database: 08/05/2026, 15:31:19 UTC
Last enriched: 08/05/2026, 17:37:10 UTC
Last updated: 09/07/2026, 23:55:32 UTC
Views: 17
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.