Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in dolyame-boxy-independent-bnpl-scheme (npm)

The npm package dolyame-boxy-independent-bnpl-scheme contained malicious code that downloads and executes platform-specific native binaries from attacker-controlled Cloudflare Workers hosts. The package impersonates the Dolyame BNPL brand but contains a generic remote-binary dropper unrelated to any legitimate functionality, granting arbitrary code execution to the operator.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system installing or importing the malicious package
Ecosystems
Attack vectors
Affected entities
  • dolyame-boxy-independent-bnpl-schemenpm package impersonating Dolyame BNPL brand

The npm package dolyame-boxy-independent-bnpl-scheme was published with malicious code designed to execute arbitrary binaries on infected systems. Upon require, the package's index.js loads setup.js, which downloads platform-specific native binaries from author-controlled Cloudflare Workers hosts, with a DNS TXT fallback via sdk.dl.wel1.ru.

The malicious code writes the downloaded binary to temporary directories (/var/tmp on Unix or %TEMP% on Windows) under disguised filenames such as .cache_ or dotnet_diag_.exe, sets executable permissions (0755), and spawns the binary detached via shell commands (/bin/sh -c on Unix or cmd.exe /c start /b on Windows).

The package employs obfuscation techniques to evade static analysis, including reconstructing destination hostnames from array-joined string fragments and splitting the require statement as require('child_'+'process'). Execution is gated by a lockfile cooldown mechanism to run once per host.

The package name impersonates the Dolyame BNPL (Buy Now Pay Later) brand, but the shipped code is a generic remote-binary dropper unrelated to any BNPL functionality, granting the operator arbitrary code execution on any machine that installs or imports the package.

Indicators of compromise

Packages
  • dolyame-boxy-independent-bnpl-scheme
Domains
  • sdk.dl.wel1.ru

Remediation

  • Immediately uninstall the dolyame-boxy-independent-bnpl-scheme package from all systems
  • Audit npm package.json and lock files for any presence of this package
  • Review system logs and process execution history for suspicious binary execution from /var/tmp or %TEMP%
  • Check for outbound connections to Cloudflare Workers hosts or sdk.dl.wel1.ru
  • Regenerate credentials and API keys on affected systems
  • Monitor for indicators of compromise from the attacker-controlled infrastructure

Sources

  1. GitHub Advisory GHSA-6qg6-c46v-jff2 · GitHub Advisory Database

Cite this entry

"Malicious code in dolyame-boxy-independent-bnpl-scheme (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-scheme-npm-rbe83s

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. containedcritical

    Malicious code in crypto-javas (npm)

    The npm package crypto-javas contains malicious code in its postinstall hook and main entrypoint that harvests environment variables (including CI secrets like AWS_*, GITHUB_TOKEN, NPM_TOKEN) and exfiltrates them to an attacker-controlled backend. The package is presented deceptively as @wizlabs/js-crypto with a placeholder repository.

    npmCompromised packageTyposquatting
  2. containedcritical

    Malicious code in flydev (npm)

    The npm package flydev contains malicious code designed to destroy Windows systems. The package masquerades as a utility but executes destructive operations including filesystem deletion, process termination, memory exhaustion, and fork bombs when invoked.

    npmCompromised package
  3. resolvedcritical

    Malicious code in ranux-dev (npm)

    ranux-dev, an npm package, contained malicious code that substituted a popular WhatsApp library dependency with arbitrary code from an unaffiliated GitHub account. The package was heavily obfuscated and designed to harvest WhatsApp sessions and credentials from installers.

    npmCompromised packageDependency confusion
  4. containedcritical

    Malicious code in npm-wold (npm)

    npm-wold@1.1.1 contains malicious code in its postinstall script that fetches remote JSON from a hardcoded endpoint and dynamically invokes attacker-controlled functions with attacker-supplied arguments, enabling code execution at install time.

    npmCompromised package