Which versions of frontend-prevent-open-redirect are malicious?

The following npm versions of frontend-prevent-open-redirect are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate frontend-prevent-open-redirect if I installed it?

Remove frontend-prevent-open-redirect from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed frontend-prevent-open-redirect — how do I know if it already compromised me?

If frontend-prevent-open-redirect 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 frontend-prevent-open-redirect part of a known attack campaign?

Yes — frontend-prevent-open-redirect is associated with the GHSA-25pv-f7c5-rjv2, RLMA-2025-05376, RLUA-2025-05802 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 frontend-prevent-open-redirect 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 frontend-prevent-open-redirect (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging frontend-prevent-open-redirect across your stack and pipelines.

Malicious package

frontend-prevent-open-redirectnpm

frontend-prevent-open-redirect is a confirmed malicious npm package (MAL-2025-48282) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in frontend-prevent-open-redirect (npm)

MAL-2025-48282

Immediate action

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

npm uninstall frontend-prevent-open-redirect

What this malware does

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.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

5d7d715ee921f7aa5445a7b69d8ee16f1c90ff529d86220f569ab70de2afa71e

3ad68243b19bbae76c8958979407439862293df1bd36ddaf4d63931bcea6a8f2

d177c27485aa0ad0a379f553c0a060dc94c15651d8bc41ad7d904dda29821d17

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for frontend-prevent-open-redirect (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging frontend-prevent-open-redirect across your stack and pipelines.
If you installed it — respond
Remove frontend-prevent-open-redirect from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If frontend-prevent-open-redirect 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 frontend-prevent-open-redirect 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. frontend-prevent-open-redirect on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-25pv-f7c5-rjv2RLMA-2025-05376RLUA-2025-05802

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks frontend-prevent-open-redirect-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database