Which versions of react-keycloak-context are malicious?

The following npm versions of react-keycloak-context are flagged malicious: 1.0.8, 1.0.9. Treat any of these as compromised.

How do I remediate react-keycloak-context if I installed it?

react-keycloak-context 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 react-keycloak-context — how do I know if it already compromised me?

If react-keycloak-context 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 react-keycloak-context part of a known attack campaign?

Yes — react-keycloak-context is associated with the GHSA-xvww-f7x6-72vx 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 react-keycloak-context 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 react-keycloak-context (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-keycloak-context across your stack and pipelines.

Malicious package

react-keycloak-contextnpm

Malicious code in react-keycloak-context (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190992

Immediate action

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

npm uninstall react-keycloak-context

What this malware does

The package react-keycloak-context 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.0.81.0.9

Indicators of compromise (SHA-256)

7d85cfa7540ee05144b01a373a457c0ca5c3fa61fc94213494fb6223427818cd

3cf006e02e42a934dd475393f106cc2cb39abb0f8438ee1a09d63d50649221c7

7af8f15e598aa54804f9774383c43f3fba0c24206f8b31e0add6b8f4100739cc

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

Campaign

GHSA-xvww-f7x6-72vx

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-keycloak-context-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