NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

veskranpm

Advisory published Updated

veskra is a confirmed malicious npm package (MAL-2026-10984) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in veskra (npm)

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

What this malware does

[email protected] contains six files with no static or behavioral indicators of supply-chain attack: no lifecycle scripts fetching remote content, no credential or environment scraping, no hardcoded exfiltration endpoints, no obfuscated payloads, and no dropper patterns. No attacker-controlled network destinations were identified.

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

4 flagged
1.0.01.0.11.0.21.0.3

Indicators of compromise (SHA-256)

4618cc8c89ff606f81079aef2e98920220ca9e59ec284c8d6c18167208604a3a
f85333fa48c61a31c9f7be395bdc5ef70596e317a3bc9124f67ece4ffcf96901
820421f16016d70b605df623be0665b3937a6197dd28a06065f50d18209ee309
ab3199001f7ba74552b3544ac400b31d1b29d752e1822b1c1b6e3ad6214f14f3
620205340530b5fd5c7d1a72c4e923d19d5ebd379bdc82bf4c921be922127764

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for veskra (4 malicious versions).

  2. If you installed it — respond

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

  3. Did it already run?

    If veskra 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. veskra on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-pr2p-6xpw-q8vwIN-MAL-2026-013205IN-MAL-2026-013295IN-MAL-2026-013296IN-MAL-2026-013294

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

veskra (npm) malicious package — MAL-2026-10984 | O3 Security