/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Researcher: counterfeit packages on the official Python repository, downloaded ~5,000 times, contained code that installed cryptomining software

Ars Technica Dan Goodin

Context & Ripple Effects

This is an early entry in a pattern the coverage keeps confirming: public package registries as a malware delivery channel. Two years earlier, researchers found 725 Ruby libraries on RubyGems carrying clipboard-stealing malware aimed at bitcoin payments, and months before this report a researcher documented GitHub Actions being abused to run cryptominers on GitHub's own infrastructure — same monetization, different entry point.

What changed here is the vector: not a compromised legitimate package but outright counterfeits uploaded to PyPI itself and pulled down roughly 5,000 times. The later arc shows the problem compounding — ctx and phpass were later compromised to steal AWS credentials, and GitGuardian found nearly 3,000 of 450,000 PyPI projects exposing credentials in code — meaning a malicious package on the registry sits on top of an existing secrets-hygiene problem that multiplies the blast radius.

First-order effects

  • Developers who installed the counterfeit packages got cryptomining software running on their machines, burning compute they paid for — and PyPI's name-trust assumption is what let ~5,000 downloads happen before detection.

Second-order effects

  • Registry operators face pressure to add package-verification and scanning layers, while the same attackers pivot across ecosystems — the RubyGems, GitHub Actions, and later ctx/phpass incidents show one technique retooled per platform rather than one-off attacks.

Third-order effects

  • If counterfeits and credential leaks keep co-occurring on PyPI, dependency resolution shifts from trusting a registry name to requiring provenance and integrity checks — and the 2026 Mistral PyPI compromise suggests the pattern extends to AI-model packages, not just libraries.

The trend: Open-source package registries are consolidating as attackers' preferred supply-chain entry point, with each incident pushing ecosystems toward provenance verification over name-based trust.

Discussion

  • @sonatype @sonatype on x
    Over the weekend we identified malicious typosquatting packages infiltrating the #PyPi repository that secretly pull in #cryptominers on the affected machines. Read more from @Ax_Sharma on what we found. https://blog.sonatype.com/... #opensource #infosec #malware
  • @ax_sharma Ax Sharma on x
    NEW: Heavily obfuscated #Python #malware caught on #opensource PyPI repo. It pulls now-deleted GitHub scripts to mine cryptocurrency on your computer. Although deleted, some of the Bash scripts could be recovered after some searching: https://blog.sonatype.com/... via @sonatype h…
  • @smdiehl Stephen Diehl on x
    Crypto is a cancer eating away at the already fragile economics of open source. https://twitter.com/...