Logo Distributed Networks Institute

Supply-Chain Attacks Against Crypto Developer Tooling

Software supply-chain attacks have become a practical way to target crypto wallets, CI/CD pipelines, and developer credentials without touching a protocol’s on-chain logic. The two cases below show different parts of the same problem: one campaign abused public troubleshooting around a Python wallet library, while another used malicious npm packages to steal credentials and spread further through compromised maintainer accounts.

Case Studies

1. Python typosquatting against bitcoinlib users

In late March 2025, researchers and bitcoinlib contributors documented malicious PyPI packages named bitcoinlibdbfix and bitcoinlib-dev. The package names referenced a real support thread in the upstream project: bitcoinlib issue #455, where users were discussing database-related errors in the clw wallet CLI.

  • Loss: Public reporting does not pin down a verified aggregate dollar loss, but researchers documented more than 39,000 downloads across the malicious packages before removal.
  • Mechanism: Typosquatting and issue-thread social engineering aimed at developers seeking a wallet-cli fix.
  • Details: The attacker published packages whose names looked like legitimate fixes for the issue discussed in public. In the same GitHub issue, a contributor warned that bitcoinlibdbfix would overwrite the clw command and exfiltrate the database file, and another participant confirmed they had checked the source code and saw the same behavior. ReversingLabs reported that both packages attempted a similar attack by replacing the legitimate clw CLI with malicious code and stealing sensitive database material from affected systems.
  • Lesson: The attack did not require compromising the legitimate bitcoinlib package; it exploited a real maintenance discussion and plausible package names instead.

2. The Shai-Hulud npm worm

A separate 2025 campaign showed how a supply-chain attack can become self-propagating once developer credentials are captured. In September 2025, CISA warned that a worm publicly known as Shai-Hulud had compromised more than 500 npm packages.

  • Loss: CISA described the blast radius as more than 500 compromised npm packages, with downstream exposure extending to any project that installed infected versions.
  • Mechanism: Credential theft followed by automated malicious republishes through compromised maintainer accounts.
  • Details: According to CISA, the malware scanned infected environments for sensitive credentials, targeted GitHub personal access tokens and cloud API keys, exfiltrated harvested secrets, uploaded stolen credentials to a public GitHub repository via the /user/repos API, and then authenticated to npm as the compromised developer to inject malicious code into other packages and publish new infected versions.
  • Lesson: Once maintainer credentials are stolen, trusted package publishers can become automated distribution points for the next wave of compromise.

Mitigations

  • Developer workflows are part of the attack surface. Public issue threads, package managers, and local CLI tools can be abused even when smart contracts are untouched.
  • Name trust is fragile. Attackers only needed package names that looked plausible in context.
  • Credential hygiene matters as much as code review. Once tokens are stolen, package publishing and repository write access can become propagation mechanisms.
  • Lockfiles and version pinning prevent automatic installation of malicious package updates.
  • Scoped publishing controls limit which maintainers can publish to specific package namespaces.
  • Phishing-resistant MFA protects maintainer accounts from credential theft.
  • Stricter CI/CD secret handling limits credential exposure in build environments.

References