Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in wallet-analytics

Malware discovered in the npm package wallet-analytics. Systems with this package installed are considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with wallet-analytics installed or running
Ecosystems
Attack vectors
Affected entities
  • wallet-analytics

The npm package wallet-analytics has been identified as containing malware. GitHub Security Advisory GHSA-xf3p-c585-94jr documents this critical supply chain incident.\n\nAny computer with wallet-analytics installed or running should be considered fully compromised. The malware may grant outside entities full control of affected systems. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected computer.\n\nWhile the package should be removed, complete remediation cannot be guaranteed due to the potential for persistent malicious software installation resulting from the initial compromise.

Indicators of compromise

Packages
  • wallet-analytics

Remediation

  • Immediately remove the wallet-analytics package from all systems
  • Rotate all secrets, keys, and credentials stored on affected computers from a different, unaffected computer
  • Perform a full security audit and malware scan of any system that had wallet-analytics installed
  • Review system logs and network activity for signs of unauthorized access or data exfiltration
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved

Sources

  1. GitHub Advisory GHSA-xf3p-c585-94jr · GitHub Advisory Database

Cite this entry

"Malware in wallet-analytics." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-wallet-analytics-1tlc9q

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 @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
  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. activecritical

    Malware in @sdgdfgdfhhhfd/multiviewr

    Malware discovered in the npm package @sdgdfgdfhhhfd/multiviewr. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  4. 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