Malicious code in dolyame-boxy-independent-bnpl-origination (npm)
The npm package dolyame-boxy-independent-bnpl-origination contained malicious code that implements a remote-payload dropper disguised as a BNPL/payment integration library. On require, the package downloads and executes arbitrary binaries from attacker-controlled Cloudflare Workers endpoints with DNS-TXT fallback channels.
- Disclosed
- Last updated
- Blast radius
- Any developer or application that installed the malicious package version(s)
- Ecosystems
- Attack vectors
- Affected entities
- dolyame-boxy-independent-bnpl-originationnpm package containing malicious code
The npm package dolyame-boxy-independent-bnpl-origination was published with malicious code that bears no relation to its stated purpose as a BNPL (Buy Now Pay Later) payment integration library. The package name was chosen to resemble legitimate payment processing tools.
Upon being required, the package's index.js loads _ext.js, which performs platform detection and constructs command-and-control (C2) hostnames by concatenating split string fragments. The malicious code then downloads an opaque binary payload from hardcoded Cloudflare Workers endpoints (oob-worker.cf99-9b3.workers.dev, cf101-adf, cf102-baf, cf103-070.workers.dev). If primary channels fail, it falls back to a DNS-TXT covert channel, retrieving base64-encoded chunks from numeric subdomains under dl.wel1.ru.
The downloaded payload is written to a disguised temporary path (/tmp/.cache_ or %TEMP%\dotnet_diag_.exe), made executable (chmod 0755 on Unix), and spawned detached via /bin/sh or cmd.exe. A state file mechanism throttles re-execution to avoid detection. This represents a complete remote-code-execution supply chain compromise.
The incident was identified by Amazon Inspector and credited to the OpenSSF's malicious-packages repository.
Indicators of compromise
- Packages
- dolyame-boxy-independent-bnpl-origination
- Domains
- oob-worker.cf99-9b3.workers.dev
- cf101-adf.workers.dev
- cf102-baf.workers.dev
- cf103-070.workers.dev
- dl.wel1.ru
Remediation
- Immediately remove the dolyame-boxy-independent-bnpl-origination package from all projects and dependencies
- Audit all systems that installed this package for signs of unauthorized binary execution or persistence mechanisms
- Review process logs and network traffic for connections to oob-worker.cf99-9b3.workers.dev, cf101-adf.workers.dev, cf102-baf.workers.dev, cf103-070.workers.dev, or DNS queries to dl.wel1.ru
- Check /tmp and %TEMP% directories for suspicious files matching patterns .cache_ or dotnet_diag_.exe
- Regenerate any credentials or secrets that may have been exposed on affected systems
- Update npm package dependencies and implement automated scanning for known malicious packages
Sources
- GitHub Advisory GHSA-7j3f-pv6r-26xp · GitHub Advisory Database
Cite this entry
"Malicious code in dolyame-boxy-independent-bnpl-origination (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malicious-code-in-dolyame-boxy-independent-bnpl-origination-npm-r87bwn
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in epic-common (npm)
The npm package epic-common was found to contain malicious code. The package was identified by Amazon Inspector and reported through the OpenSSF malicious packages database.
npmCompromised package - resolvedcritical
Malware in @zynkit/jwtbytes
Malware was discovered in the npm package @zynkit/jwtbytes, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - containedcritical
Malware in userbotjs
The npm package userbotjs contained malware that could fully compromise any system on which it was installed. The advisory recommends treating affected systems as fully compromised and rotating all secrets and keys from a different computer.
npmCompromised package - resolvedcritical
Malicious code in epic-common-node (npm)
The npm package epic-common-node was found to contain malicious code. The package has been identified and reported through GitHub Security Advisory GHSA-m36g-mhjr-ww2c.
npmCompromised package