Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in dolyame-boxy-fonts

Malware discovered in the npm package dolyame-boxy-fonts. The package grants full system compromise to attackers. All affected systems should be considered fully compromised and all secrets rotated from a clean machine.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed
Ecosystems
Attack vectors
Affected entities
  • dolyame-boxy-fonts

A critical malware incident has been identified in the npm package dolyame-boxy-fonts. According to the GitHub advisory, any computer with this package installed or running should be considered fully compromised.

The malware provides attackers with full control of affected systems. Users are advised to immediately rotate all secrets and keys from a different, unaffected computer. While the package should be removed, complete remediation cannot be guaranteed due to the level of system access the malware may have obtained.

This is a supply chain attack via a compromised package in the npm ecosystem.

Indicators of compromise

Packages
  • dolyame-boxy-fonts

Remediation

  • Immediately remove the dolyame-boxy-fonts package from all systems
  • Rotate all secrets, API keys, credentials, and authentication tokens from a clean, unaffected computer
  • Assume full system compromise and conduct forensic analysis
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider rebuilding affected systems from clean media if possible
  • Monitor for any unauthorized access or activity on accounts that may have been compromised

Sources

  1. GitHub Advisory GHSA-rphf-wm4q-p6rj · GitHub Advisory Database

Cite this entry

"Malware in dolyame-boxy-fonts." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-dolyame-boxy-fonts-16wt2u

Suggest a correction

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

  1. 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
  2. containedcritical

    Malware in @junofficial/baileys

    The npm package @junofficial/baileys contained malware that fully compromised any system with the package installed or running. The malicious package has been identified and removed from distribution.

    npmCompromised package
  3. activecritical

    Malware in @zynkit/probe

    Malware discovered in the npm package @zynkit/probe. Systems with this package installed or running are considered fully compromised, with potential for complete system takeover.

    npmCompromised package
  4. activecritical

    Malware in agentsync-pkg

    Malware discovered in the npm package agentsync-pkg. 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