Malicious code in dolyame-boxy-block (npm)
The npm package dolyame-boxy-block version 35.5.2 contains malicious code that executes remote code on any system importing it. It downloads and runs attacker-controlled binaries from obfuscated hostnames or retrieves payloads via DNS TXT records, then writes and executes these payloads on the local machine. The package's advertised functionality does not match its behavior, indicating deliberate deception. This results in full-host remote code execution upon requiring or importing the package.
AI Analysis
Technical Summary
The npm package [email protected] includes a _runtime.js module that is automatically loaded and reconstructs obfuscated attacker-controlled hostnames to fetch binaries via HTTPS. These binaries are saved to temporary directories with decoy filenames, permissioned, and executed detached from the parent process. If HTTPS retrieval fails, the package uses a DNS TXT record covert channel to fetch base64-encoded payload chunks from specific domains, reassembles them, and executes the payload similarly. The package's claimed purpose as a UI library is a cover for this malicious behavior, which leads to full remote code execution on any system that imports the package.
Potential Impact
Any consumer that requires or imports [email protected] triggers full remote code execution on their host. This allows attackers to execute arbitrary code with the privileges of the importing process, potentially leading to complete system compromise. The malicious payload is fetched dynamically from attacker-controlled infrastructure, making detection and prevention difficult. The obfuscation of hostnames and use of DNS covert channels further complicate detection.
Mitigation Recommendations
No official patch or remediation is currently available for [email protected]. Users should immediately cease using this package and remove it from their projects. Avoid importing or requiring this package in any environment. Monitor dependency trees to ensure this package is not included transitively. Consider using trusted package sources and verifying package integrity before installation. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates.
Malicious code in dolyame-boxy-block (npm)
Description
The npm package dolyame-boxy-block version 35.5.2 contains malicious code that executes remote code on any system importing it. It downloads and runs attacker-controlled binaries from obfuscated hostnames or retrieves payloads via DNS TXT records, then writes and executes these payloads on the local machine. The package's advertised functionality does not match its behavior, indicating deliberate deception. This results in full-host remote code execution upon requiring or importing the package.
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 npm package [email protected] includes a _runtime.js module that is automatically loaded and reconstructs obfuscated attacker-controlled hostnames to fetch binaries via HTTPS. These binaries are saved to temporary directories with decoy filenames, permissioned, and executed detached from the parent process. If HTTPS retrieval fails, the package uses a DNS TXT record covert channel to fetch base64-encoded payload chunks from specific domains, reassembles them, and executes the payload similarly. The package's claimed purpose as a UI library is a cover for this malicious behavior, which leads to full remote code execution on any system that imports the package.
Potential Impact
Any consumer that requires or imports [email protected] triggers full remote code execution on their host. This allows attackers to execute arbitrary code with the privileges of the importing process, potentially leading to complete system compromise. The malicious payload is fetched dynamically from attacker-controlled infrastructure, making detection and prevention difficult. The obfuscation of hostnames and use of DNS covert channels further complicate detection.
Mitigation Recommendations
No official patch or remediation is currently available for [email protected]. Users should immediately cease using this package and remove it from their projects. Avoid importing or requiring this package in any environment. Monitor dependency trees to ensure this package is not included transitively. Consider using trusted package sources and verifying package integrity before installation. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13298
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a73852fbf8831d5394f062f
Added to database: 08/05/2026, 18:47:11 UTC
Last enriched: 08/05/2026, 21:32:34 UTC
Last updated: 09/14/2026, 13:57:29 UTC
Views: 18
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.