Which versions of svelte-autocomplete-select are malicious?

The following npm versions of svelte-autocomplete-select are flagged malicious: 1.1.1. Treat any of these as compromised.

How do I remediate svelte-autocomplete-select if I installed it?

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

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

Yes — svelte-autocomplete-select is associated with the GHSA-gmj5-76gr-38p9 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-autocomplete-select 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-autocomplete-select (version 1.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging svelte-autocomplete-select across your stack and pipelines.

Malicious package

svelte-autocomplete-selectnpm

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

MAL-2025-191016

Immediate action

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

npm uninstall svelte-autocomplete-select

What this malware does

The package svelte-autocomplete-select 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

1 flagged

1.1.1

Indicators of compromise (SHA-256)

960b186f377ba501f7f2b250cf287429e5854e0997861b5192dc82f902f69872

9659f91ce1f699661cdedee2d6691f0a4a515b4941511290b0082e5b662a91ea

79731ba572c474ee7ad75931f1ba12e51491c062cb9ad23b8c5a6a3fc0500d93

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

Campaign

GHSA-gmj5-76gr-38p9

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks svelte-autocomplete-select-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