Which versions of use-feature-flags-plugin are malicious?

The following npm versions of use-feature-flags-plugin are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate use-feature-flags-plugin if I installed it?

Remove use-feature-flags-plugin 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 use-feature-flags-plugin — how do I know if it already compromised me?

If use-feature-flags-plugin 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 use-feature-flags-plugin part of a known attack campaign?

Yes — use-feature-flags-plugin is associated with the GHSA-jccf-63c2-rpf3, RLMA-2026-02057 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 use-feature-flags-plugin 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 use-feature-flags-plugin (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 use-feature-flags-plugin across your stack and pipelines.

Malicious package

use-feature-flags-pluginnpm

Malicious code in use-feature-flags-plugin (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2660

Immediate action

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

npm uninstall use-feature-flags-plugin

What this malware does

The package use-feature-flags-plugin 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

99.0.0

Indicators of compromise (SHA-256)

660732143ccd386ddaddd4f9427bd90addde06757ef650afa82bd2313d02c9eb

990dff76e7eb5c08f1acb20aa9d86599674963bddcc36c11a5a314d6ff7c8d49

b176246976f266320b17cb9aa3a4fdddb6970d6f115637cb5cb2224c2db75c7e

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 use-feature-flags-plugin (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 use-feature-flags-plugin across your stack and pipelines.
If you installed it — respond
Remove use-feature-flags-plugin 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 use-feature-flags-plugin 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 use-feature-flags-plugin 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. use-feature-flags-plugin 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-jccf-63c2-rpf3RLMA-2026-02057

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks use-feature-flags-plugin-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