Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in base65-13x

The npm package base65-13x was found to contain malware, resulting in full system compromise of any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • base65-13x

The npm package base65-13x was identified as containing malware. According to the GitHub Advisory (GHSA-fp83-xcpx-v3qm), any computer that has this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different computer. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the package installation, as the outside entity may have gained full control of the system.\n\nAffected package: base65-13x (npm).

Indicators of compromise

Packages
  • base65-13x

Remediation

  • Immediately remove the base65-13x package from all systems
  • Rotate all secrets, keys, and credentials from a different, unaffected computer
  • Assume full system compromise and conduct forensic analysis
  • Review system logs for unauthorized access or activity
  • Consider full system rebuild if critical infrastructure is affected

Sources

  1. GitHub Advisory GHSA-fp83-xcpx-v3qm · GitHub Advisory Database

Cite this entry

"Malware in base65-13x." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 11, 2026; last updated August 11, 2026. https://supplychainattack.org/incident/malware-in-base65-13x-1qd8ck

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 github-policy-bot (npm)

    The npm package github-policy-bot contained malicious code that exfiltrated host identifiers and environment metadata during installation via a postinstall script. The package name shadowed a legitimate Google-owned repository and was authored under a placeholder account claiming security research purposes.

    npmCompromised packageTyposquatting
  2. 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
  3. 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
  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