# MAL-2026-13961: Malicious code in velora-kit (npm)


- **Type:** Malicious package
- **Package:** `velora-kit` (npm)
- **Published:** 13 Aug 2026
- **Also known as:** GHSA-c48p-mmxp-3g9c

## What is MAL-2026-13961?

MAL-2026-13961 is a malicious package in velora-kit, published on 13 Aug 2026. 

### Official description

velora-kit@12.0.2 exports a getPlugin() function that fetches content from a hardcoded bare-IP endpoint at https://31.97.137.157:45000/icons/116 and passes the response's `data.credits` field to `new Function(...)`, which is then invoked with `require`, `module`, `process`, `Buffer`, and `Promise` injected — executing attacker-controlled JavaScript with full Node.js privileges in the consumer's process. Variable naming (protocol/domain/path split, `bearrtoken: 'logo'`, `token: '116'`) is styled to resemble a CDN icon fetcher while actually constructing a URL to a bare-IP host and evaluating the returned payload as code. The declared dependency set (@primno/dpapi for Windows DPAPI decryption, better-sqlite3/sqlite3 for browser-profile database reads, node-machine-id, socket.io-client, request, axios) provides the fetched second-stage code with capabilities aligned to credential and wallet theft from local browser profiles.

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-13961?

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-13961 is a malicious package: velora-kit (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-13961/ (Markdown: https://insights.sbomify.com/MAL-2026-13961/index.md)
```

## Sources

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

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