Which versions of velora-kit are malicious?

The following npm versions of velora-kit are flagged malicious: 12.0.2, 12.1.2. Treat any of these as compromised.

How do I remediate velora-kit if I installed it?

velora-kit is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed velora-kit — how do I know if it already compromised me?

If velora-kit was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is velora-kit part of a known attack campaign?

Yes — velora-kit is associated with the IN-MAL-2026-017657, IN-MAL-2026-017656 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find velora-kit across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for velora-kit (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging velora-kit across your stack and pipelines.

Malicious package

velora-kitnpm

velora-kit is a confirmed malicious npm package (MAL-2026-13961) that steals credentials and exfiltrates sensitive data (malicious versions 12.0.2, 12.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in velora-kit (npm)

MAL-2026-13961

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall velora-kit

What this malware does

[email protected] 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.

Malicious versions

2 flagged

12.0.212.1.2

Indicators of compromise (SHA-256)

a60310ccbaf263dc4333db7ecb716cbf5f5ae13a2cfc9d8b7416f82e4561d7bb

e8e2fc9f701feadf6fb4677ac234a9750261162c33aa46153fd9acbfbfe43c3c

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for velora-kit (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging velora-kit across your stack and pipelines.
If you installed it — respond
velora-kit is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If velora-kit was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks velora-kit before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. velora-kit on npm has been identified as a malicious package (versions 12.0.2, 12.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017657IN-MAL-2026-017656

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks velora-kit-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database