Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

veloqnpm

Advisory published Updated

veloq is a confirmed malicious npm package (MAL-2026-14566) that typosquats a legitimate package to trick installs (malicious versions 1.0.1, 1.0.2, 1.1.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in veloq (npm)

MAL-2026-14566
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall veloq

What this malware does

[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.

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.

Malicious versions

7 flagged
1.0.11.0.21.1.01.1.31.2.11.2.21.2.3

Indicators of compromise (SHA-256)

aec9a4513d507544ac89ac6fa13523ea603e88cd4a0d8c455e6002c8b7f984a2
058b0f85e80ad1893e8546161034450eaac2165d5eb7299710f0870bc26b05b2
098cbf855445d7385aae2a54f61f48866cdc3e90e6cb196f10a73b1c23705457
461a89d9079a4df94e090f130836cd29c4d90829bf066c28ebf262e3840e1552
6a072cf37dd12aa4f24bd0f25a9a52589d3f35daae13f6f031474ae596a33ab4
8ce36425f527e5db3ce0498ed502182dd2a5d8945016fc42d849848c64a82867
d51bc1d102134ed41b5a38c7a8013da22569da272cf7fd1ee924b9961698599a
eff50298ab575a1674b32755a5a0fb7db8e3c35f5c07eecec50e7d22893f0b87

Detection & response playbook

Typosquat
  1. Find it

    Search your lockfiles and build artifacts for veloq (7 malicious versions).

  2. If you installed it — respond

    veloq is a typosquat — you almost certainly intended a legitimately-named package. Remove veloq, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If veloq was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. veloq on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.1.0, 1.1.3, 1.2.1, 1.2.2, 1.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gccc-9phc-w64pIN-MAL-2026-019189IN-MAL-2026-019188IN-MAL-2026-019196IN-MAL-2026-019197IN-MAL-2026-019198IN-MAL-2026-019200IN-MAL-2026-019199

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks veloq-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

veloq (npm) malicious package — MAL-2026-14566 | O3 Security