NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@fishingbooker/react-swipernpm

Advisory published Updated

@fishingbooker/react-swiper is a confirmed malicious npm package (MAL-2025-191224) that steals credentials and exfiltrates sensitive data (malicious version 0.1.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @fishingbooker/react-swiper (npm)

MAL-2025-191224
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @fishingbooker/react-swiper

What this malware does

The package @fishingbooker/react-swiper 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.1.5

Indicators of compromise (SHA-256)

ea430a5c66c8d03735c6125308c678277bf269ff36bf9c53442c6ffe4042bc09
7c1643e65862f62373bbf8eb60965b55463a85cbf26d34e940366b088f1d015b
06f57ab28c32fa764c92d001b6c970f064bf1c5544959b2c677d8ce8f26d3bd5
2662da90915d018058575bc29be7e76f548bc25485d889d7cc9a46932ddce1e6

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @fishingbooker/react-swiper (version 0.1.5).

  2. If you installed it — respond

    @fishingbooker/react-swiper 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 @fishingbooker/react-swiper 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. @fishingbooker/react-swiper on npm has been identified as a malicious package (version 0.1.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vx4f-7jpj-8q6gRLMA-2025-06023

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @fishingbooker/react-swiper-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@fishingbooker/react-swiper (npm) malicious package — MAL-2025-191224 | O3 Security