What each feed carried across the trailing 24 months
Every malicious advisory in the VDB is classified into exactly one of four feeds: OSSF Malicious Packages (published to OSV.dev, built for SCA scanners), OpenSourceMalware (a commercial catalogue, ingested per user API key), Vulnesis CLI Malscan (standalone GCVE-110 findings, built for SOC detection), and the remaining enriched Vulnesis VDB corpus, which spans more ecosystems than any single upstream feed. Advisories, IOC samples and actionable IOCs are additive; packages and actors are counted distinct within each ecosystem-month bucket. Actionable IOCs exclude the bare package-identifier types (a name, typosquat or version).
Live figures are briefly unavailable. The classification and analysis below stand on their own; the tables populate when the feed refreshes.
What "Vulnesis VDB (enriched)" means
This bucket is not a single upstream feed. It is malicious-package advisories aggregated from other databases, GitLab, Snyk, Gemnasium, GitHub (GHSA) and OSV, each of which, like OSSF, publishes primarily name-level records for SCA scanners. Vulnesis ingests and enriches them, adding the hashes, hosts, install commands and attribution the original advisory never carried, on records that arrived carrying none. A scanner reading the raw upstream advisory cannot act on that; it would have to enrich the data itself, or query a source like the Vulnesis VDB that already has.
A note on the OpenSourceMalware figures. OpenSourceMalware is a commercial threat-intelligence catalogue, the "open source" is the subject (malware in open-source packages), not the licence. Under our agreement Vulnesis ingests OSM data only for users who supply their own OSM API key, so the advisories shown here are the slice our users unlocked, not OSM's full catalogue. Vulnesis has also donated malware data back to OSM across several ecosystems.
Explore OpenSourceMalware → · Add your OSM API key to Vulnesis to widen this coverage.
The exposure window: how long is a malicious package installable before OSSF flags it?
We resolved when each malicious package was first published (deps.dev historical index plus the npm and PyPI registries) and compared it to the advisory's publish date, across 2858 OSSF npm packages and 142 PyPI packages. The gap is how long the package sat installable before anyone was warned.
- 38% of flagged npm packages were already deleted, or their original publish record erased on takedown, by the time we looked.
- Median exposure among the 62% still placeable on a timeline was 510 days; 63% had been installable for over a year.
- On PyPI, 89% of checked packages were already gone from the registry entirely.
By the time an OSSF advisory reaches you the damage is done: anyone who installed the package during the window is already compromised, and the advisory is a post-mortem, not a warning.
Closing the window: Malscan at install time
Vulnesis Malscan runs at install time inside the Package Firewall, checking every package against this same intelligence before it reaches your build, so a malicious dependency is blocked as it installs, not catalogued a year later. Registries and platform teams can also run the Malscan CLI on demand, before publishing, to confirm they are not shipping malware into their own build systems or downstream to their customers.
Method: first-publish via the deps.dev API; advisory date from the OSV record. Packages absent from deps.dev, or whose only surviving record post-dates the advisory, are reported deleted/erased. Baseline snapshot, July 2026; live figures replace it as the VDB enrichment builds a representative sample.
Two audiences: SCA scanners and SOC teams
A malware advisory only helps a scanner if it ships something machine-readable: a hash, a domain, an install command, an attacker account. Counting the actionable indicators per feed shows which reporting a defender can act on.
Built for different jobs
OSSF Malicious Packages and OSV are built for SCA scanners: is this installed dependency on a known-bad list, by name? Vulnesis ingests those MAL- advisories and enriches them, then adds SOC-grade detection and attribution on top through OpenSourceMalware, Vulnesis CLI Malscan and the enriched Vulnesis VDB.
What the trailing 24 months showed
Across the window the four feeds reported 0 malware advisories over 0 packages. Of the 0 IOC samples, only 0 were actionable indicators, and those, with the 0 attributed actors, came overwhelmingly from Vulnesis's own scanning and enrichment rather than the high-volume, name-only upstream advisories. Those advisories are useful, they feed an SCA scanner a blocklist, but they arrive after the fact: most flagged packages had been installable for months, and many were already gone by the time anyone was warned. The value is in the indicators, the attribution and the timing, and that is what the Vulnesis VDB and the install-time Package Firewall are built to carry.
Advisories, IOC samples and actionable IOCs are additive; packages and actors are counted distinct within each ecosystem-month bucket. Actionable IOCs exclude bare package-identifier types.
Know a package is malicious before it installs
The Vulnesis Package Firewall checks every install against this same malware intelligence, across 25 registries, before the dependency reaches your build. The malicious domains, IPs and URLs behind these counts are also published as free STIX 2.1 feeds.
Start for free · See the Package Firewall · Malware campaigns and threat actors