Which versions of svelte-toasty are malicious?

The following npm versions of svelte-toasty are flagged malicious: 1.1.2, 1.1.3. Treat any of these as compromised.

How do I remediate svelte-toasty if I installed it?

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

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

Yes — svelte-toasty is associated with the GHSA-chwq-g27w-8pfr 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-toasty 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-toasty (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging svelte-toasty across your stack and pipelines.

Malicious package

svelte-toastynpm

Malicious code in svelte-toasty (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191017

Immediate action

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

npm uninstall svelte-toasty

What this malware does

The package svelte-toasty was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged

1.1.21.1.3

Indicators of compromise (SHA-256)

33e60836cd791de23038b867cd4e97fb21298208fc87c6b2096fe0e189d3fc86

cd148faed79826bf40f8bee2ac4f3aee5c75ec85e9ca81d1a9ed972db4a17a26

c64a56a77de8c314feb25cf78026e45d88739cdaa1b6811d1a069ff7de49c780

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-toasty (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging svelte-toasty across your stack and pipelines.
If you installed it — respond
svelte-toasty 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-toasty 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-toasty 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-toasty on npm has been identified as a malicious package (versions 1.1.2, 1.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-chwq-g27w-8pfr

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks svelte-toasty-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