Which versions of react-native-log-level are malicious?

The following npm versions of react-native-log-level are flagged malicious: 1.2.1, 1.2.2. Treat any of these as compromised.

How do I remediate react-native-log-level if I installed it?

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

If react-native-log-level 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-native-log-level part of a known attack campaign?

Yes — react-native-log-level is associated with the GHSA-3pcc-7gj8-5h47 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-native-log-level 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-native-log-level (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-native-log-level across your stack and pipelines.

Malicious package

react-native-log-levelnpm

Malicious code in react-native-log-level (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191000

Immediate action

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

npm uninstall react-native-log-level

What this malware does

The package react-native-log-level 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.2.11.2.2

Indicators of compromise (SHA-256)

b30d43b06bd70b8708ef6d7f3925c984ef8e5632d2b813d0de6286c5e3bb79d9

24d9b4b32f8ecb8d86fe3786c14e216538d2d25e1e3257627f186495dedaf9b1

9a0067e0646ee3349ef8087c6d587d7c4a3deaac1f66c62d3c04457fda10bc4b

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

Campaign

GHSA-3pcc-7gj8-5h47

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-native-log-level-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