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 @fleetbo/svro (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-14586

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (0d86373813cd4d2b65edb11f6a3f352ad81a55e7de0444884f66b0adb482e661) The package ships two heavily obfuscated JavaScript files under dist/ — postinstall.cjs and cli.cjs — using hex-mangled identifiers (_0x56260b, _0x12d644, etc.) characteristic of javascript-obfuscator output. The corresponding non-minified variants (dist/postinstall.js and dist/cli.js) combine require('child_process') with outbound POST HTTP calls at the top level of a postinstall entry point, meaning the code executes automatically on `npm install` and can both spawn processes on the installer's host and send data to a network endpoint. Obfuscation of a postinstall lifecycle script that has both process-spawning and HTTP-POST primitives is not consistent with any legitimate build, native-binary fetch, or telemetry pattern — legitimate postinstalls do not need to hide their control flow. The combination of automatic install-time execution, deliberate code obfuscation, and reachable child_process + outbound HTTP primitives is the fingerprint of an install-time dropper or exfiltration payload. ## Source: ghsa-malware (5a08b2bf7b6dbcd5fa506c02f8ad63d38c5db835ef8f7e1cf90ef8b5d95a80d7) 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
28 Aug 2026 03:09:30 UTC
Source modified
28 Aug 2026 19:45:31 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 06:49 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current