Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in ts-vitest (npm)

Exploitation and risk

Source status

CISA 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-10990

Published

ts-vitest is a typosquat of vitest/ts-eslint (hollow "kelly-calc"/"clob-math" content, no legitimate functionality) that ships a postinstall two-stage fetch-exec dropper. The package.json declares `postinstall: node scripts/install-check.cjs`; the hook's `resolvePeerBundleUrl()` fetches a JSON config from a hardcoded, typosquatting host (`https://ts-eslint.vercel.app/config/clob-math.json`, also the package.json homepage), reads a second-stage tarball URL out of that config, npm installs the tarball, then `require()`s and executes it — achieving install-time RCE before any package code is used. The config JSON resolves to a second-stage tarball at `https://ts-eslint.vercel.app/releases/psm-peer.tgz`, whose `main` entry point is `peer-math.js`. The config indirection (an ephemeral *.vercel.app host serving JSON that points at the real payload) keeps the tarball URL out of the package bytes, defeating a naive grep for a hardcoded payload URL. The lineage alternates malicious and clean releases: 1.1.1 shipped the dropper (previously convicted), 1.1.2 removed the postinstall hook as a clean decoy, and 1.1.3 restores a byte-identical copy of the 1.1.1 dropper. The hook is entirely YARA-invisible (0 matches); detection required reading the hook's logic directly rather than relying on signature scoring. Published by sole npm maintainer `naradi` (maintainer email `[email protected]`), who pushed 7 versions in ~6.5 hours. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (082ff0d6388a0e04c300f34025d389e37e4378fd863105399c10d1395294e657) The package is published as `ts-vitest` and its README advertises a TypeScript/Jest transformer, but the shipped code is unrelated (a Kelly-stake helper) and the postinstall hook performs install-time remote code execution. On `npm install`, the postinstall resolves a bundle URL from a JSON config at `https://ts-eslint.vercel.app/config/clob-math.json` (a lookalike of the legitimate `typescript-eslint` project), downloads the returned `.tgz` archive, extracts it, runs `npm install` inside the extracted directory, then `require`s `peer-math.js` and invokes `syncSession()` in the installer's Node process. There is no version pin, no hash or signature check, and the config host is author-controlled and mutable, so the executed payload can be changed at any time. The name/README cover story combined with the typosquat-style config domain is a deliberate dropper shape. ## Source: ghsa-malware (122dc63f875d72ec5998d5f1f34e84dfa1e49dd17ba586852e8961aff09a2739) 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
21 Jul 2026 00:00:00 UTC
Source modified
26 Aug 2026 01:18:19 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.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 20 Nov 22:12 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current