# MAL-2026-14566: Malicious code in veloq (npm)


- **Type:** Malicious package
- **Package:** `veloq` (npm)
- **Published:** 27 Aug 2026
- **Also known as:** GHSA-gccc-9phc-w64p

## What is MAL-2026-14566?

MAL-2026-14566 is a malicious package in veloq, published on 27 Aug 2026. 

### Official description

veloq@1.1.0 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.

## What should I do about MAL-2026-14566?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-14566 is a malicious package: veloq (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-14566/ (Markdown: https://insights.sbomify.com/MAL-2026-14566/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-14566

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-14566/
Summaries are generated and may contain mistakes; the official description above is the record.