Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@seung-ju/react-native-action-sheetnpm

Malicious code in @seung-ju/react-native-action-sheet (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190915
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @seung-ju/react-native-action-sheet

What this malware does

The package @seung-ju/react-native-action-sheet 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
0.2.1

Indicators of compromise (SHA-256)

4a093775c06aa43c37f1449879903040ac8d4670967b0fc9931be9fc842d3c72
bfe11e98ae51b1881aecb8397e3e0eae1c7531701a7f8d39f982ae95db27eb83
942a67851b1e7913b505447a80b66fe35ae6e1ab6e9b08c7c496c2605e06df16

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @seung-ju/react-native-action-sheet (version 0.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @seung-ju/react-native-action-sheet across your stack and pipelines.

  2. If you installed it — respond

    @seung-ju/react-native-action-sheet 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.

  3. Did it already run?

    If @seung-ju/react-native-action-sheet 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.

  4. How O3 protects you

    O3 blocks @seung-ju/react-native-action-sheet 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. @seung-ju/react-native-action-sheet on npm has been identified as a malicious package (version 0.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-57w6-8vg8-qwwf

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @seung-ju/react-native-action-sheet-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