Which versions of twitch-security are malicious?

Every published version of twitch-security on npm is considered malicious. Remove the package entirely.

How do I remediate twitch-security if I installed it?

Remove twitch-security from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed twitch-security — how do I know if it already compromised me?

If twitch-security 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.

Is twitch-security part of a known attack campaign?

Yes — twitch-security is associated with the GHSA-gp4w-hqqj-mj8j 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 twitch-security across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for twitch-security (all published versions).

Malicious package

twitch-securitynpm

Advisory published Mar 13, 2026Updated Mar 23, 2026

twitch-security is a confirmed malicious npm package (MAL-2026-1416) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in twitch-security (npm)

MAL-2026-1416

Immediate action

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

npm uninstall twitch-security

What this malware does

The package twitch-security 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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

f46d2713d7df72180db5cb77dcd0cefbbffa8baa5a245e376ab250a84d29fc23

4f99261d9b844b178048388c92a488b23fa3bf806bbedbcc40108cb97f0b7087

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for twitch-security (all published versions).
If you installed it — respond
Remove twitch-security from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If twitch-security 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. twitch-security on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gp4w-hqqj-mj8j

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks twitch-security-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database