Which versions of @flipster/utils are malicious?

The following npm versions of @flipster/utils are flagged malicious: 88.8.8. Treat any of these as compromised.

How do I remediate @flipster/utils if I installed it?

Remove @flipster/utils 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 @flipster/utils — how do I know if it already compromised me?

If @flipster/utils 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 @flipster/utils part of a known attack campaign?

Yes — @flipster/utils is associated with the GHSA-6r97-q2pc-v98m 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 @flipster/utils 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 @flipster/utils (version 88.8.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @flipster/utils across your stack and pipelines.

Malicious package

@flipster/utilsnpm

Malicious code in @flipster/utils (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-249

Immediate action

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

npm uninstall @flipster/utils

What this malware does

The package @flipster/utils 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.

The OpenSSF Package Analysis project identified '@flipster/utils' @ 88.8.8 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

88.8.8

Indicators of compromise (SHA-256)

3e6efe1f57ff67b4d32af2331c5ced43082944cbc2dd3e1f020e32f587408750

7959db4a5848d904daa027ec759ca4588e6c033f1df17a82686a3d28d2dd2e9f

0490c6f411da9b1fa5efbfd1cad8e7b41ec915751813279fb2a89a0f5e967524

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

Campaign

GHSA-6r97-q2pc-v98m

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @flipster/utils-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