Malicious code in chai-as-synced (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-6497
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (be17d22b28dc53ea46085190c1f5ff11ae16ce4b80539162d68c2ad2b224158e) [email protected] impersonates the pino logger: it ships pino's README, LICENSE, docs/, index.d.ts and lib/ file layout (proto.js, levels.js, redaction.js, transport.js, worker.js, tools.js, multistream.js) with pino's keywords (`fast`,`logger`,`stream`,`json`), while package.json declares an unrelated name and author (Robert King <[email protected]>, bugs URL https://jsonspack.com/issues) and a boilerplate description unrelated to logging. index.js unconditionally executes `require('./lib/config')` at module top level. lib/config.js is not pino's config module; it is a ~4MB single-line obfuscator.io bundle (rotated string array of ~23,868 entries, hex-escaped identifiers, control-flow flattening, nested decoder functions) that auto-runs the moment any consumer imports the package. The package also declares `axios ^1.10.0` as a runtime dependency although the visible wrapper (a no-op express middleware) has no HTTP use, positioning the hidden payload to perform network I/O at import. The combination of deceptive identity, hidden obfuscated payload, import-time auto-execution, and a bundled HTTP client is a covert-code-execution shape inconsistent with any legitimate logging library. ## Source: ghsa-malware (40194d8b76beed1c302e92600d56ab077089dc5db4790851e20326587ebc7f3d) 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
- 26 Jun 2026 02:51:34 UTC
- Source modified
- 8 Sep 2026 00:30:16 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.