Which versions of @fishingbooker/react-swiper are malicious?

The following npm versions of @fishingbooker/react-swiper are flagged malicious: 0.1.5. Treat any of these as compromised.

How do I remediate @fishingbooker/react-swiper if I installed it?

@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.

I already installed @fishingbooker/react-swiper — how do I know if it already compromised me?

If @fishingbooker/react-swiper 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 @fishingbooker/react-swiper part of a known attack campaign?

Yes — @fishingbooker/react-swiper is associated with the GHSA-vx4f-7jpj-8q6g, RLMA-2025-06023 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 @fishingbooker/react-swiper 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 @fishingbooker/react-swiper (version 0.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @fishingbooker/react-swiper across your stack and pipelines.

Malicious package

@fishingbooker/react-swipernpm

Malicious code in @fishingbooker/react-swiper (npm) Remove it immediately and rotate any exposed credentials.

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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @fishingbooker/react-swiper (version 0.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @fishingbooker/react-swiper across your stack and pipelines.
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.
Did it already run?
If @fishingbooker/react-swiper 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 @fishingbooker/react-swiper 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. @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.

Malware detection Runtime egress monitoring