Live supply-chain malware tracker

Confirmed malicious packages on npm, PyPI, RubyGems, crates.io and other registries, with hijacks of widely used packages first.

Generated by VEDAS from the OpenSSF malicious-packages database via OSV, as of 2026-11-01 20:37 UTC. Checked every few hours. How this works.

Hijacked widely used packages

An established package with real usage that shipped a malicious version: the pattern behind the axios, chalk, debug, nx and TanStack attacks. If any of these is in your lockfiles, follow its alert.

By ecosystem

Smaller existing packages that turned malicious

Packages with a clean release history that then published malware, but with low usage. Some were taken over; others were built up slowly before turning. Usage is the registry’s current figure.

Packages created to attack (newest 100)

Typosquats, lookalikes and packages that were malicious from their first release. Names are shown as text, not links, so nobody installs one by accident.

How this works

• Only confirmed records. Every row is a published MAL- record in the OpenSSF malicious-packages database, which merges reports from GitHub, Amazon Inspector, OpenSSF Package Analysis and security vendors. Nothing is inferred, and withdrawn records are dropped.
• Widely used and hijacked means the package was published at least 90 days before the first malicious version, had at least 3 clean releases before it, and is widely used: 10,000 or more weekly downloads on npm, 1,000,000 or more monthly downloads on PyPI, 1,000,000 or more total downloads on RubyGems, or 100,000 or more recent downloads on crates.io.
• Smaller existing packages meet the same history rule with lower usage. Created to attack is everything else.
• Alerts. Each hijacked widely used package that no advisory already covers gets an automated alert page in the supply-chain advisories and the RSS feed.

Public malware records lag the attack itself. Our measurements, from the malicious publish to the first MAL- record:

That gap is where researchers post on X and Telegram first. Closing it means watching the registries directly; the plan is in how this site works.