Malicious code in bnpl-blocks-atom-bnpl-checkbox (npm)
The npm package bnpl-blocks-atom-bnpl-checkbox version 35.6.1 contains malicious code that downloads and executes a platform-specific binary payload from multiple obfuscated and unrelated network destinations. The payload is fetched without any version pinning or signature verification, saved to a temporary file with executable permissions, and executed detached from the main process. The package also contains dormant code with similar behavior that is currently unreachable. The obfuscation techniques and use of unrelated hosts indicate an attempt to evade static analysis and conceal malicious activity.
AI Analysis
Technical Summary
The malicious code in [email protected] uses an asynchronous bootstrap in _polyfill.js to reconstruct network destinations from obfuscated string fragments, then downloads a binary payload from Cloudflare Workers hosts and fallback domains. It writes the payload to a temporary file, sets executable permissions, and spawns it detached via a shell command. Additionally, lib/telemetry.js contains dormant code with the same drop-and-execute pattern, though it is not currently reachable from the main entry point. The obfuscation of child_process import and hostnames serves as evasion against static detection. No integrity checks or version pinning are present, increasing risk.
Potential Impact
This malicious package can execute arbitrary code on the host system by downloading and running an external binary payload without user consent or verification. This can lead to compromise of the host environment, unauthorized access, or further malware deployment. The presence of dormant similar code suggests potential for additional malicious functionality. There are no known exploits in the wild reported yet, but the capability for remote code execution is significant.
Mitigation Recommendations
No official patch or remediation is currently available for this package version. Users should immediately avoid using bnpl-blocks-atom-bnpl-checkbox version 35.6.1 and remove it from their environments. Consider auditing dependencies for malicious code and replacing this package with a trusted alternative. Monitor for updates from the package maintainer or npm advisories for any future fixes. Since this is not a cloud service, remediation depends on user action.
Malicious code in bnpl-blocks-atom-bnpl-checkbox (npm)
Description
The npm package bnpl-blocks-atom-bnpl-checkbox version 35.6.1 contains malicious code that downloads and executes a platform-specific binary payload from multiple obfuscated and unrelated network destinations. The payload is fetched without any version pinning or signature verification, saved to a temporary file with executable permissions, and executed detached from the main process. The package also contains dormant code with similar behavior that is currently unreachable. The obfuscation techniques and use of unrelated hosts indicate an attempt to evade static analysis and conceal malicious activity.
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 malicious code in [email protected] uses an asynchronous bootstrap in _polyfill.js to reconstruct network destinations from obfuscated string fragments, then downloads a binary payload from Cloudflare Workers hosts and fallback domains. It writes the payload to a temporary file, sets executable permissions, and spawns it detached via a shell command. Additionally, lib/telemetry.js contains dormant code with the same drop-and-execute pattern, though it is not currently reachable from the main entry point. The obfuscation of child_process import and hostnames serves as evasion against static detection. No integrity checks or version pinning are present, increasing risk.
Potential Impact
This malicious package can execute arbitrary code on the host system by downloading and running an external binary payload without user consent or verification. This can lead to compromise of the host environment, unauthorized access, or further malware deployment. The presence of dormant similar code suggests potential for additional malicious functionality. There are no known exploits in the wild reported yet, but the capability for remote code execution is significant.
Mitigation Recommendations
No official patch or remediation is currently available for this package version. Users should immediately avoid using bnpl-blocks-atom-bnpl-checkbox version 35.6.1 and remove it from their environments. Consider auditing dependencies for malicious code and replacing this package with a trusted alternative. Monitor for updates from the package maintainer or npm advisories for any future fixes. Since this is not a cloud service, remediation depends on user action.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13527
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a75f710bf8831d53984faaa
Added to database: 08/07/2026, 15:17:36 UTC
Last enriched: 08/07/2026, 15:37:23 UTC
Last updated: 09/22/2026, 02:00:27 UTC
Views: 22
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.