Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malicious code in dolyame-boxy-atom-bnpl-navigation-arrow (npm)

The npm package dolyame-boxy-atom-bnpl-navigation-arrow contains malicious code that downloads and executes platform-specific binaries from attacker-controlled Cloudflare Workers hosts, with a DNS-TXT fallback channel. The package name pattern suggests a typosquat or dependency-confusion attack.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any developer or application that installed or required the dolyame-boxy-atom-bnpl-navigation-arrow package; potential for lateral movement and supply chain propagation.
Ecosystems
Attack vectors
Affected entities
  • dolyame-boxy-atom-bnpl-navigation-arrownpm package containing malicious code in index.js and _bridge.js

The npm package dolyame-boxy-atom-bnpl-navigation-arrow was found to contain malicious code in its index.js and bridge.js files. Upon require(), the package unconditionally executes a setup routine that attempts to download platform-specific executables from attacker-controlled Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev). The hostnames are reconstructed at runtime using split string fragments to evade detection.\n\nThe downloaded binaries are written to temporary directories (/var/tmp on Unix, %TEMP% on Windows) under names mimicking legitimate artifacts (dotnet_diag.exe on Windows, .cache_ on Unix), made executable (chmod 0755), and launched detached via shell commands. When HTTPS retrieval fails, the malware falls back to a DNS-TXT covert channel, querying TXT records against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru to retrieve payload chunks, which are base64-decoded and executed.\n\nThe malware uses obfuscation techniques including splitting the child_process module name ("child_"+"process") to evade static analysis, and gates execution with a ~19958-second cooldown and environment variable checks (DISABLE_TELEMETRY, DO_NOT_TRACK). The package name and version pattern are consistent with a typosquat or dependency-confusion attack vector.

Indicators of compromise

Packages
  • dolyame-boxy-atom-bnpl-navigation-arrow
Domains
  • oob-worker.cf103-070.workers.dev
  • oob-worker.cf101-adf.workers.dev
  • oob-worker.cf102-baf.workers.dev
  • sdk.dl.wel1.ru
  • ext.dl.wel1.ru
  • pkg.dl.wel1.ru
  • net.dl.wel1.ru

Remediation

  • Immediately remove the dolyame-boxy-atom-bnpl-navigation-arrow package from all projects and dependencies
  • Audit npm package.json and lock files for any installations of this package
  • Review and revoke any credentials or secrets that may have been exposed on affected systems
  • Monitor systems that installed this package for signs of unauthorized binary execution or network connections to the attacker-controlled domains
  • Block outbound connections to oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, and the wel1.ru DNS domains at the network perimeter
  • Implement npm package verification and scanning in CI/CD pipelines to detect malicious packages before installation

Sources

  1. GitHub Advisory GHSA-2jf7-g5cc-rp7c · GitHub Advisory Database

Cite this entry

"Malicious code in dolyame-boxy-atom-bnpl-navigation-arrow (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 7, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-dolyame-boxy-atom-bnpl-navigation-arrow-npm-1jdvu5

Suggest a correction

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

  1. resolvedcritical

    Malicious code in akamai-sensor (npm)

    A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.

    npmCompromised packageTyposquatting
  2. resolvedcritical

    Malicious code in depcruise-wrap-stream-in-html (npm)

    depcruise-wrap-stream-in-html@99.9.1 is a malicious npm package that mimics an internal helper of dependency-cruiser. It is a hollow package that downloads and executes arbitrary code from a Google Cloud Storage bucket during installation.

    npmCompromised packageDependency confusionTyposquatting
  3. resolvedcritical

    Malicious code in @finaxis/common-js (npm)

    The npm package @finaxis/common-js was published with a README and keywords copied from lodash v4.18.1, but contained a heavily obfuscated Xelis (XEL) proof-of-work cryptominer instead of lodash functionality. Consumers installing this package would unknowingly run a covert CPU/GPU miner on their systems.

    npmCompromised packageTyposquatting
  4. resolvedcritical

    Malicious code in wct-st (npm)

    The npm package wct-st contained malicious code in its postinstall lifecycle script that collected and exfiltrated host identifiers to a remote endpoint. The package name resembles the deprecated web-component-tester, consistent with a typosquatting attack.

    npmCompromised packageTyposquatting