Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in dolyame-boxy-independent-bnpl-cards

Malware discovered in the npm package dolyame-boxy-independent-bnpl-cards. 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-cards

The npm package dolyame-boxy-independent-bnpl-cards 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-cards

Remediation

  • Immediately remove the dolyame-boxy-independent-bnpl-cards package from all affected systems
  • Rotate all secrets, keys, and credentials from a different, uncompromised computer
  • Assume full system compromise and conduct forensic analysis
  • Monitor affected systems for signs of persistent malware or unauthorized access
  • Consider rebuilding affected systems from clean media if possible

Sources

  1. GitHub Advisory GHSA-j8fg-fh4m-2cw2 · GitHub Advisory Database

Cite this entry

"Malware in dolyame-boxy-independent-bnpl-cards." 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-cards-1ye29k

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 3-buildsight-web (npm)

    The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.

    npmCompromised package
  2. resolvedcritical

    Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)

    Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.

    npmDependency confusionCompromised package
  3. resolvedcritical

    Malicious code in create-coin (npm)

    create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.

    npmCompromised packageTyposquatting
  4. resolvedcritical

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

    The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.

    npmCompromised package