Malicious code in tailwindcss-form-components (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-12223
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ae9425c630e8b36b03993f6124066f178a86a285ae44e5e4590016ac575c4cac) index.js exposes getPlugin(), which performs an HTTP GET to http://46.183.25.232:45000/icons/106, parses the JSON response, and passes the `credits` field to `new Function(...)` with `require`, `module`, `process`, and `Buffer` injected — giving the remote endpoint full Node.js execution privileges on the consumer's host. The destination URL is assembled from split string fragments (protocol/separator/domain/path) and framed with icon/CDN-style naming (`iconDomain`, `bearrtoken: 'logo'`, path segment `icons/`), while a separate setDefaultModule function references a benign-looking cdnjs/font-awesome URL as a decoy. The package name typosquats the tailwindcss ecosystem, and declared dependencies include @primno/dpapi, better-sqlite3, and node-machine-id — libraries associated with Windows credential/DPAPI access, browser SQLite database reads, and host fingerprinting. The transport is plain HTTP to a bare IP with no integrity check, so the executed payload is attacker-controlled and mutable. ## Source: ghsa-malware (e81bbba31caeec4daee576d481d25be697795b026010c8f341e251bbcdc71031) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
- Source published
- 5 Aug 2026 09:05:44 UTC
- Source modified
- 24 Sep 2026 09:10:32 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
osv · MAL-2026-13348
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d9a1a1a5f0fd81e6ba6198e7f4cbdeab1c16b8ceed3dbb7becc6b4b6f611ad52) [email protected] runs `node index.js` from an npm install lifecycle hook, which loads `./lib/core` and constructs a subdomain from the installer's OS username, hostname, and current working directory (with a timestamp and the static prefix `asnbank`), then issues a `dns.resolve4()` query against `<prefix>.<user>.<host>.<cwd>.<ts>.oob.sl4x0.xyz`. This leaks installer identity via DNS to an out-of-band canary domain on every install. The destination host `oob.sl4x0.xyz` and API surface (`os`, `dns`, `process`, `userInfo`, `hostname`, `cwd`) are hidden as hex code-point arrays reconstructed with `String.fromCharCode` in sibling modules `lib/b02e30.js` and `lib/6ad264.js`. The README explicitly claims 'No network requests', which directly contradicts the observed install-time DNS beacon. ## Source: ghsa-malware (50b6f54438d307adc9e47e195f892bd555eacb68771cdd2bae6bd1252d190bd1) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
- Source published
- 5 Aug 2026 15:41:20 UTC
- Source modified
- 24 Sep 2026 09:10:32 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
osv · MAL-2026-13356
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (94e40493af5310c6ee769911bff65e55538911ae3f286fba2a3474f9f8a38940) [email protected] is a trojan package presenting itself as a chai plugin (README shows `chai.use(chaiLeaf)`) while its badges, documentation, and internal version metadata (`lib/meta.js` exports version `9.6.0`) are copied from the pino logger. The package's main entry `index.js` immediately loads `./lib/config`, a 3.5MB file that is heavily obfuscated with obfuscator.io-class transforms: a rotated string array of 20,855 entries, two runtime decoder functions, tens of thousands of decoder-wrapper indirections, and control-flow flattening (104,934 deobfuscation changes reported by webcrack). The file begins with a top-level IIFE, so its opaque body runs automatically the moment any consumer calls `require('chai-foundry')`. All destinations and string constants are reconstructed at runtime, so the payload's network endpoints and behaviors are hidden from static inspection. The combination of identity impersonation, mismatched metadata, and a multi-megabyte control-flow-flattened import-time loader in a package advertised as a small chai plugin is the canonical shape of a hostile npm dropper/stealer. ## Source: ghsa-malware (7493f27a9dde87cd284125de3d582e1cd94870a2c4bac65ae9c6f1d764dfbee0) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
- Source published
- 5 Aug 2026 16:37:52 UTC
- Source modified
- 24 Sep 2026 09:10:32 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.