Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in dolyame-boxy-independent-bnpl-scheme

Malware discovered in the npm package dolyame-boxy-independent-bnpl-scheme. Systems with this package installed are considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • dolyame-boxy-independent-bnpl-scheme

The npm package dolyame-boxy-independent-bnpl-scheme has been identified as containing malware. According to the GitHub advisory, any computer with this package installed or running should be considered fully compromised, indicating the malware grants broad system access to an outside entity.\n\nThe advisory recommends immediate removal of the package and rotation of all secrets and keys from a different, uncompromised computer. However, due to the level of system compromise, there is no guarantee that package removal alone will eliminate all malicious software that may have been installed as a result of the initial compromise.

Indicators of compromise

Packages
  • dolyame-boxy-independent-bnpl-scheme

Remediation

  • Remove the dolyame-boxy-independent-bnpl-scheme package immediately
  • Rotate all secrets, keys, and credentials from a different, uncompromised computer
  • Assume full system compromise and conduct a thorough security audit
  • Consider rebuilding affected systems from clean media if possible
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration

Sources

  1. GitHub Advisory GHSA-4c3q-jjpc-xjwp · GitHub Advisory Database

Cite this entry

"Malware in dolyame-boxy-independent-bnpl-scheme." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-dolyame-boxy-independent-bnpl-scheme-awnjsc

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 rust-testing-utils (npm)

    The npm package rust-testing-utils contained malicious code that impersonates the pino logger and executes remotely-fetched code with arbitrary privileges. The package spawns a child process that decodes a hardcoded URL, fetches attacker-controlled content, and executes it via Function constructor with full module-loading capability.

    npmCompromised packageMalicious commit
  2. containedcritical

    Malicious code in stillm4ddpocs-demo-sprocket (npm)

    The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.

    npmCompromised packageDependency confusion
  3. containedcritical

    Malicious code in @syncraft-labs/react (npm)

    The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.

    npmCompromised package
  4. containedcritical

    Malware in hydration-dim-kit

    Malware was discovered in the npm package hydration-dim-kit. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.

    npmCompromised package