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

svelte-streak-kitnpm

svelte-streak-kit is a confirmed malicious npm package (MAL-2026-13679) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in svelte-streak-kit (npm)

MAL-2026-13679
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall svelte-streak-kit

What this malware does

[email protected] was scanned across 8 files with no a static rule matches and no traced behaviors indicating credential access, exfiltration, install-time remote code execution, silent relay, dropper activity, or persistence. No lifecycle scripts, network calls to attacker-controlled destinations, or obfuscated payloads were identified in the package contents.

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

1 flagged
1.0.0

Indicators of compromise (SHA-256)

e85a74ba93af51a80d66996947352cdb86175d21c8db850c778f2641d56ced1b
2172e0671582a6e9c3359cd893cb96a7a09706ae0670208ddfbc82636a828fed

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    svelte-streak-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.

  3. Did it already run?

    If svelte-streak-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.

  4. How O3 protects you

    O3 blocks svelte-streak-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. svelte-streak-kit on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2w6v-q693-8jjmIN-MAL-2026-017217

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks svelte-streak-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.

Explore

svelte-streak-kit (npm) malicious package — MAL-2026-13679 | O3 Security