Vant NPM Package Malicious Versions Published
Is it fixed? Not yet.
Ongoing since Nov 18, 03:30 UTC. First reported Nov 18, 03:30 UTC. Not on the vendor’s status page yet.
What happened
Ten malicious versions of the vant npm package (2.13.3, 2.13.4, 2.13.5, 3.6.13, 3.6.14, 3.6.15, 4.9.11, 4.9.12, 4.9.13, and 4.9.14) were published by user landluck, introducing malicious install hooks.
What caused it?
Malicious code and install hooks ('postinstall': 'node lib/utils/support.js') were added to multiple versions of the vant package.
Source: github.com
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on security advisory
vant (npm): malicious versions 2.13.3, 2.13.4, 2.13.5, 3.6.13, 3.6.14, 3.6.15, 4.9.11, 4.9.12, 4.9.13, 4.9.14 published
Source
Evidence
1 report · 1 CVEShow
- [1]CVE First reportvant (npm): malicious versions 2.13.3, 2.13.4, 2.13.5, 3.6.13, 3.6.14, 3.6.15, 4.9.11, 4.9.12, 4.9.13, 4.9.14 published(opens security advisory in a new tab)
Malicious code in vant (npm, 111,071 downloads last week), affected: 2.13.3, 2.13.4, 2.13.5, 3.6.13, 3.6.14, 3.6.15, 4.9.11, 4.9.12, 4.9.13, 4.9.14. Malicious code in vant (npm). Ten versions of vant were published on 2024-12-19 between 00:41:47Z and 01:49:30Z by the npm user landluck, using npm 9.2.0: 4.9.11, 2.13.3, 3.6.13, 4.9.12, 3.6.14, 2.13.4, 4.9.13, 4.9.14, 3.6.15 and 2.13.5. Each one adds an install hook, "postinstall": "node lib/utils/support.js", which no earlier release of vant…
by GitHub Advisory Database 0upvotes 0comments
FAQ
What happened in the npm issue?
Ten malicious versions of the vant npm package (2.13.3, 2.13.4, 2.13.5, 3.6.13, 3.6.14, 3.6.15, 4.9.11, 4.9.12, 4.9.13, and 4.9.14) were published by user landluck, introducing malicious install hooks.
What is affected by the npm issue?
npm (versions: 2.13.3, 2.13.4, 2.13.5, 3.6.13, 3.6.14, 3.6.15, 4.9.11, 4.9.12, 4.9.13, 4.9.14).
When did the npm issue start and end?
It started Nov 18, 03:30 UTC and is still ongoing (1 d 1 h so far). This page updates as it develops.
How do I get alerts for npm?
Subscribe to the npm RSS feed for every new npm incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether npm is down. npm feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.