Thirteen npm packages, 48 seconds, one fake wallet SDK

A coordinated attack on the npm registry dumped 13 counterfeit Coinbase-style wallet SDK packages in just 48 seconds, showing how fast malicious code can masquerade as trusted tooling. Developers who install a package based only on a familiar name can unwittingly inject a fake SDK into their apps.

The packages appeared between 04:54:59 and 04:55:48 UTC on 7 September 2026. Names like cb-wallet-http and scw-core echo the official @coinbase/wallet-sdk namespace. Instead of typo-squatting, the attackers prefixed the names with familiar strings, hoping a teammate’s recommendation or a forum post would convince users of their legitimacy.

All 13 releases shared the same skeletal configuration: version 0.0.1-security, an empty maintainer list, and the default npm metadata shown immediately after publishing. The identical setup points to a single script that churned out the packages, a hallmark of automation rather than manual effort.

npm’s open publishing model lets anyone upload a package without prior review, enabling attacks like this. Past supply-chain incidents have shown that once malicious code lands in a dependency tree, it runs on every machine that installs it.

NPM has not identified the perpetrators or explained how the code spread beyond the initial uploads. It is also unclear whether the attackers aimed at Coinbase users specifically or simply flooded the registry with plausible-looking names, hoping some would be adopted.

What developers can do now

  • Check a package’s publisher before adding it; official SDKs live under verified organization scopes.
  • Run tools that scan dependencies for known malicious signatures.
  • Pin exact versions in lockfiles and avoid pulling newly published packages without review.
  • Prefer registries that require two-factor authentication for maintainers.

What to watch

  • Whether npm tightens vetting for packages that mimic well-known brands.
  • Community-driven blacklists that flag impersonating names.
  • Updates from security researchers on any active exploitation of the 13 fake SDKs.

The episode proves that a familiar-sounding name offers no guarantee of safety. Vigilance and verification remain the strongest defenses against supply-chain attacks in the open-source ecosystem.