Malicious code in dwhetlfront-dwhetlfront-core (npm)
The npm package dwhetlfront-dwhetlfront-core version 35.8.1 contains malicious code that downloads and executes platform-specific payloads from external Cloudflare worker hosts. It writes these payloads to temporary directories with disguised filenames, sets executable permissions, and runs them detached from the main process. The code uses obfuscation techniques such as string concatenation and dynamic hostname reconstruction to evade static analysis. A secondary dropper exists in the package but is not invoked in this version. No patch or remediation information is provided.
AI Analysis
Technical Summary
The dwhetlfront-dwhetlfront-core npm package version 35.8.1 includes malicious functionality triggered upon require() of the package. The main script index.js loads a support script that selects a platform-specific payload URL and downloads executable bytes from Cloudflare workers.dev hosts, with a DNS-TXT fallback mechanism. These bytes are saved to temporary directories under misleading filenames, permissions are set to executable (chmod 0755), and the payload is spawned detached from the main process using shell commands. Hostnames and API names are dynamically reconstructed via string concatenation to evade static detection. Additionally, a parallel dropper implementation exists in lib/telemetry.js but is not executed in this version. No official patch or fix is indicated in the data.
Potential Impact
This malicious package can lead to arbitrary code execution on the host system by downloading and running external payloads without user consent. The payloads are executed detached from the main process, potentially allowing persistent or stealthy malicious activity. The obfuscation techniques used complicate detection and analysis. There is no indication of active exploitation in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory or npm registry for current remediation guidance. Until a fix or removal is confirmed, avoid using version 35.8.1 of dwhetlfront-dwhetlfront-core. Consider removing the package from your environment and scanning for any dropped payloads or related artifacts.
Malicious code in dwhetlfront-dwhetlfront-core (npm)
Description
The npm package dwhetlfront-dwhetlfront-core version 35.8.1 contains malicious code that downloads and executes platform-specific payloads from external Cloudflare worker hosts. It writes these payloads to temporary directories with disguised filenames, sets executable permissions, and runs them detached from the main process. The code uses obfuscation techniques such as string concatenation and dynamic hostname reconstruction to evade static analysis. A secondary dropper exists in the package but is not invoked in this version. No patch or remediation information is provided.
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 dwhetlfront-dwhetlfront-core npm package version 35.8.1 includes malicious functionality triggered upon require() of the package. The main script index.js loads a support script that selects a platform-specific payload URL and downloads executable bytes from Cloudflare workers.dev hosts, with a DNS-TXT fallback mechanism. These bytes are saved to temporary directories under misleading filenames, permissions are set to executable (chmod 0755), and the payload is spawned detached from the main process using shell commands. Hostnames and API names are dynamically reconstructed via string concatenation to evade static detection. Additionally, a parallel dropper implementation exists in lib/telemetry.js but is not executed in this version. No official patch or fix is indicated in the data.
Potential Impact
This malicious package can lead to arbitrary code execution on the host system by downloading and running external payloads without user consent. The payloads are executed detached from the main process, potentially allowing persistent or stealthy malicious activity. The obfuscation techniques used complicate detection and analysis. There is no indication of active exploitation in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory or npm registry for current remediation guidance. Until a fix or removal is confirmed, avoid using version 35.8.1 of dwhetlfront-dwhetlfront-core. Consider removing the package from your environment and scanning for any dropped payloads or related artifacts.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13202
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a738536bf8831d5394f0b99
Added to database: 08/05/2026, 18:47:18 UTC
Last enriched: 08/05/2026, 19:00:23 UTC
Last updated: 08/05/2026, 20:11:49 UTC
Views: 3
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.