Which versions of svelte-kit-cache are malicious?

The following npm versions of svelte-kit-cache are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate svelte-kit-cache if I installed it?

svelte-kit-cache 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 svelte-kit-cache — how do I know if it already compromised me?

If svelte-kit-cache 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 svelte-kit-cache part of a known attack campaign?

Yes — svelte-kit-cache is associated with the GHSA-9fg7-rqp2-7hpg, IN-MAL-2026-017227 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 svelte-kit-cache 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 svelte-kit-cache (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-kit-cache across your stack and pipelines.

Malicious package

svelte-kit-cachenpm

svelte-kit-cache is a confirmed malicious npm package (MAL-2026-13677) 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-kit-cache (npm)

MAL-2026-13677

Immediate action

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

npm uninstall svelte-kit-cache

What this malware does

No static or behavioral indicators of supply-chain attack were observed in this package version. No lifecycle scripts fetching or executing remote content, no credential or environment scraping, no hardcoded exfiltration endpoints, and no obfuscated payloads were identified across the scanned files.

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)

3693c930557492daa60f894ec7c21501081f3230da12c25847912e51da49d1ff

4ea03ff1abc711e776243e207270c0f7d208521386cc87d94fbb8d64300beb9d

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 svelte-kit-cache (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-kit-cache across your stack and pipelines.
If you installed it — respond
svelte-kit-cache 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 svelte-kit-cache 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 svelte-kit-cache 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-kit-cache 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-9fg7-rqp2-7hpgIN-MAL-2026-017227

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks svelte-kit-cache-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