Researcher created typo versions of popular programming language packages to execute code on 17K hosts
Edit: It seems that the blog post and the thesis caused quite some interest. Please contact me under the following mail address, since my mail server on this VPS is constantly down :/ tschachn [| Tweets: @tdierks Tweets: Tim Dierks / @tdierks : Package managers are disasters from a security/threat standpoint. Here's a beautiful demonstration of the tire fire. http://incolumitas.com/...
Context & Ripple Effects
This 2016 experiment is the early proof-of-concept for a decade-long pattern: a researcher showed that simply registering misspelled names of popular packages was enough to get code executed on roughly 17,000 hosts, and Tim Dierks' widely shared reaction framed package managers as 'disasters from a security/threat standpoint.' What began as an academic demonstration has since been industrialized by attackers.
The corpus traces the escalation: dependency confusion attacks hitting Microsoft, Zillow, and Lyft showed namespace collisions could be weaponized at scale, while a package named after a ChatGPT hallucination pulled 30K+ downloads in three months — and by 2025 criminals were compromising maintainer accounts directly, as in the Aikido Security report on 18 malware-laced npm packages.
First-order effects
- Developers who mistyped a package name handed the researcher code execution on their machines — the same mechanism later used for theft rather than measurement, affecting anyone installing from public indexes without name verification.
Second-order effects
- Registry operators and popular-package maintainers are pushed toward defensive responses — reserving typo variants, scanning new submissions — because every successful demo lowers the barrier for copycats, as the slopsquatting wave around AI-hallucinated names shows.
Third-order effects
- If the pattern holds, the open source trust model itself becomes the attack surface: isolated demos converge into sustained campaigns like TeamPCP's compromise of over 1,000 packages, forcing the ecosystem to treat package distribution as a verified supply chain rather than a naming convention.
The trend: Package registry abuse is maturing from researcher demonstrations into a structural weakness of open source distribution, where whoever controls a plausible package name controls the machines that install it.