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 veloq (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-14566

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (058b0f85e80ad1893e8546161034450eaac2165d5eb7299710f0870bc26b05b2) [email protected] is a near-verbatim fork of gulplog rebranded by 'Blockvora Team', with two injected lines inside getLogger() in index.js: a call to sigcheck.saveLog('favorite.png', 'veloq', 12467) and require('./log'). The './log' file is not present in the package tarball (the manifest's files array lists only LICENSE and index.js), so the require will only resolve if sigcheck.saveLog has written it to the package directory as a side effect. This is the dropper shape: an unrelated dependency is invoked with a filename-like argument and a numeric offset at import time, and the wrapper then loads a sibling module that only exists after that call. The dependency, the filename ('favorite.png'), and the numeric key are unrelated to logging, and the package's README and API surface impersonate gulpjs/gulplog while the repository and author metadata point at blockvora/veloq, consistent with a lookalike used as cover for the injected trigger. Any consumer that does require('veloq') executes this code path at load time. ## Source: ghsa-malware (aec9a4513d507544ac89ac6fa13523ea603e88cd4a0d8c455e6002c8b7f984a2) 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
27 Aug 2026 13:51:36 UTC
Source modified
31 Aug 2026 18:31:26 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 03:39 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current