Which versions of flip-prx are malicious?

The following npm versions of flip-prx are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate flip-prx if I installed it?

Remove flip-prx 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 flip-prx — how do I know if it already compromised me?

If flip-prx 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 flip-prx part of a known attack campaign?

Yes — flip-prx is associated with the GHSA-vj8r-7f53-45wq, RLMA-2026-01323 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 flip-prx 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 flip-prx (version 1.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging flip-prx across your stack and pipelines.

Malicious package

flip-prxnpm

Malicious code in flip-prx (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-321

Immediate action

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

npm uninstall flip-prx

What this malware does

The package flip-prx 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.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

7490a8c35552395560296cfd74b57dc93c222f1bc067d02a1c92d1ec180b7bfa

51518ff5a54220f9558ab04c5bad0ac14e14ee3aff6c92b54c1b727e1a90f4b7

0a8a54cd5ad82d74204208b3d80642e93962945b1adb0425af70ccab07b6d57d

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 flip-prx (version 1.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging flip-prx across your stack and pipelines.
If you installed it — respond
Remove flip-prx 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 flip-prx 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 flip-prx 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. flip-prx on npm has been identified as a malicious package (version 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vj8r-7f53-45wqRLMA-2026-01323

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks flip-prx-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