The npm package dolyame-boxy-atom-bnpl-email-form version 20.3.3 includes a malicious runtime script (_runtime.js) that dynamically selects a platform-specific payload path and fetches an opaque binary payload from multiple obfuscated Cloudflare Workers domains. This payload is saved to system temporary directories under disguised filenames, permissions are set to executable (chmod 0755), and the payload is executed detached via child_process.spawn using shell commands. If HTTPS-based payload retrieval fails, the package falls back to a covert DNS TXT record channel, resolving specific domains to retrieve base64-encoded payload chunks, which are concatenated, decoded, written, and executed similarly. The package attempts to evade static analysis by assembling hostnames, fallback domains, and critical strings like 'child_process' at runtime from split string arrays. No integrity checks such as version pinning, hash verification, or signature validation are present, and the payload sources are external and unrelated to the publisher. The package falsely advertises itself as an Analytics SDK with a telemetry opt-out, which does not align with its actual behavior.

This malicious package can execute arbitrary binary payloads on the host system by downloading and running code from attacker-controlled infrastructure. This can lead to unauthorized code execution, potential system compromise, and persistence. The use of covert DNS channels for payload delivery increases stealth and complicates detection. The lack of integrity checks and external payload sources heightens risk. The disguised filenames and detached execution further aid evasion of detection and analysis.

No official patch or remediation is currently documented. Users should avoid using version 20.3.3 of dolyame-boxy-atom-bnpl-email-form. Remove the package from affected systems and replace it with trusted alternatives. Monitor for suspicious child processes spawned from npm packages. Since no vendor advisory or patch information is available, patch status is not yet confirmed — check the vendor advisory for current remediation guidance.