Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in solana-address-codec

Malware was discovered in the npm package solana-address-codec. Systems with this package installed are considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the malicious package installed
Ecosystems
Attack vectors
Affected entities
  • solana-address-codecnpm package containing malware

A critical malware incident was identified in the npm package solana-address-codec. The malicious package grants full control of affected systems to an outside entity.\n\nAny computer with this package installed or running should be considered fully compromised. All secrets and keys stored on affected systems should be rotated immediately from a different, unaffected computer. While the package should be removed, complete removal of all malicious software cannot be guaranteed due to the level of system compromise.\n\nUsers should assume that any credentials, private keys, or sensitive data on affected systems have been exposed and take immediate action to secure their accounts and assets.

Indicators of compromise

Packages
  • solana-address-codec

Remediation

  • Immediately remove the solana-address-codec package from all systems
  • Rotate all secrets, private keys, and credentials from a different, unaffected computer
  • Assume full system compromise and consider rebuilding affected systems from clean media
  • Audit all account activity and transactions for unauthorized access
  • Monitor for any signs of continued malicious activity on affected systems

Sources

  1. GitHub Advisory GHSA-9jx5-jcp6-qmqq · GitHub Advisory Database

Cite this entry

"Malware in solana-address-codec." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 7, 2026; last updated July 7, 2026. https://supplychainattack.org/incident/malware-in-solana-address-codec-8r3kcy

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 typescirpt-cli (npm)

    The npm package typescirpt-cli (a typosquat of typescript-cli) contained malicious code in its postinstall script that downloads and executes a binary (main.exe) on Windows and WSL systems, and exfiltrates system metadata to a hardcoded IP address.

    npmTyposquattingCompromised package
  2. containedcritical

    Malicious code in typescipt-core (npm)

    The npm package typescipt-core (a typosquat of typescript) contained malicious postinstall code that downloads and executes a second-stage payload on Windows and WSL systems. The dropper exfiltrates host profile information to 193.70.34.101:20099 before fetching attacker-controlled executables.

    npmCompromised packageTyposquatting
  3. containedcritical

    Malicious code in typesript-cli (npm)

    The npm package 'typesript-cli' (a one-character typosquat of 'typescript') contains malicious code in its postinstall script that downloads and executes a Windows PE binary, and can cross the Linux/WSL sandbox boundary to execute payloads on the Windows host. The script also beacons to a hardcoded IP endpoint.

    npmTyposquattingCompromised package
  4. resolvedcritical

    Malicious code in @mohamed_nowisar/depconf-canary-test (npm)

    The npm package @mohamed_nowisar/depconf-canary-test contained malicious code in its preinstall hook that automatically collected and exfiltrated host and CI environment information to an attacker-controlled webhook endpoint without user consent.

    npmCompromised package