Which versions of react-scrambled-text are malicious?

The following npm versions of react-scrambled-text are flagged malicious: 1.0.4, 1.0.5. Treat any of these as compromised.

How do I remediate react-scrambled-text if I installed it?

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

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

Yes — react-scrambled-text is associated with the GHSA-wpc4-3h4p-fwj5 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-scrambled-text 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-scrambled-text (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-scrambled-text across your stack and pipelines.

Malicious package

react-scrambled-textnpm

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

MAL-2025-191415

Immediate action

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

npm uninstall react-scrambled-text

What this malware does

The package react-scrambled-text 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.41.0.5

Indicators of compromise (SHA-256)

36daec950ebd2a4d753cf8c489bdf35eb6464204a88c503531feb56465dc1508

e7bd2e39bc9ff3a0b7417bca4372483100e950eeb2b116b61779e0bceeccf135

47a16f2f1c129f61cd9bb2e821b552e648edde237088c472e55e4ee8efd1ecf4

3888a54f9c5c14abb5fd0b64ec41778b1bc989da36cd5e48a480514eb81b9e57

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-scrambled-text (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-scrambled-text across your stack and pipelines.
If you installed it — respond
react-scrambled-text 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-scrambled-text 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-scrambled-text 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-scrambled-text on npm has been identified as a malicious package (versions 1.0.4, 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wpc4-3h4p-fwj5

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-scrambled-text-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