Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in clawtrl-wallet (npm)

The npm package clawtrl-wallet contained malicious code that reads environment variables and system information, spawns bash subprocesses, and makes outbound HTTPS requests—consistent with credential-stealing behavior. The package name appears designed to impersonate a legitimate wallet utility.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Unknown; depends on installation count and whether credentials were exfiltrated from affected systems.
Ecosystems
Attack vectors
Affected entities
  • clawtrl-walletnpm package containing malicious code designed to steal credentials and environment data

The npm package clawtrl-wallet was found to contain malicious code in its cli.js file. The code imports child_process, https, and os modules, then reads process.env and system information via os APIs (os.tmpdir and related functions), spawns bash subprocesses, and issues outbound HTTPS requests.\n\nThis behavior pattern—environment and system-data exfiltration paired with bash execution and external network communication—is consistent with credential and wallet-stealing malware rather than legitimate wallet library functionality. Legitimate wallet packages have no legitimate reason to shell out to bash or transmit environment contents off-host.\n\nThe package name itself suggests impersonation of a wallet utility, likely intended to deceive installers into running the malicious code. The malicious code was identified by Amazon Inspector and credited to the OpenSSF malicious-packages repository.

Indicators of compromise

Packages
  • clawtrl-wallet

Remediation

  • Immediately uninstall clawtrl-wallet from all systems where it was installed
  • Audit npm package.json and lock files for any references to clawtrl-wallet and remove them
  • Rotate all credentials and secrets that may have been exposed on affected systems
  • Review environment variables and system logs on affected machines for signs of unauthorized access
  • Use npm audit to check for other malicious packages in your dependency tree
  • Implement package verification and allowlisting policies to prevent installation of typosquatted or impersonated packages

Sources

  1. GitHub Advisory GHSA-fh5c-3w68-67m4 · GitHub Advisory Database

Cite this entry

"Malicious code in clawtrl-wallet (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malicious-code-in-clawtrl-wallet-npm-1yijox

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 checkout-desktop-total (npm)

    The npm package checkout-desktop-total contained malicious code that executes a hidden loader on import, downloading and running platform-specific native payloads from attacker-controlled Cloudflare Workers hosts or reconstructing them via DNS TXT records under wel1.ru. Any system that imported this package should be considered compromised.

    npmCompromised package
  2. resolvedcritical

    Malicious code in epic-sso (npm)

    The npm package epic-sso was found to contain malicious code. The package was identified by Amazon Inspector and reported through the OpenSSF malicious packages database.

    npmCompromised package
  3. resolvedcritical

    Malicious code in epic-common-node (npm)

    The npm package epic-common-node was found to contain malicious code. The package has been identified and reported through GitHub Security Advisory GHSA-m36g-mhjr-ww2c.

    npmCompromised package
  4. containedcritical

    Malicious code in pfp-forms-sme-loan (npm)

    The npm package pfp-forms-sme-loan contains malicious code that executes a hidden loader on import, downloading and running platform-specific native payloads from attacker-controlled Cloudflare Workers hosts or reconstructing them via DNS TXT records under well1.site. Any system that imported this package should be considered compromised.

    npmCompromised packageMalicious commit