Which versions of @gpbw-fcop-ui-packages/theme are malicious?

The following npm versions of @gpbw-fcop-ui-packages/theme are flagged malicious: 10.0.9. Treat any of these as compromised.

How do I remediate @gpbw-fcop-ui-packages/theme if I installed it?

Remove @gpbw-fcop-ui-packages/theme 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 @gpbw-fcop-ui-packages/theme — how do I know if it already compromised me?

If @gpbw-fcop-ui-packages/theme was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @gpbw-fcop-ui-packages/theme part of a known attack campaign?

Yes — @gpbw-fcop-ui-packages/theme is associated with the RLMA-2026-04728, RLUA-2026-05868 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 @gpbw-fcop-ui-packages/theme across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @gpbw-fcop-ui-packages/theme (version 10.0.9).

Malicious package

@gpbw-fcop-ui-packages/themenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@gpbw-fcop-ui-packages/theme is a confirmed malicious npm package (MAL-2026-7071) that executes malicious code on install (malicious version 10.0.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @gpbw-fcop-ui-packages/theme (npm)

MAL-2026-7071

Immediate action

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

npm uninstall @gpbw-fcop-ui-packages/theme

Malicious versions

1 flagged

10.0.9

Indicators of compromise (SHA-256)

8e77d8ceb6da79d630e50a61014f46ea48038a8813a1c17b129cf8a5870cb5aa

ec3c05998f479bb257e47d18010939c86d554d8c57422dbd05bdf146bc2e42f7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @gpbw-fcop-ui-packages/theme (version 10.0.9).
If you installed it — respond
Remove @gpbw-fcop-ui-packages/theme 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 @gpbw-fcop-ui-packages/theme was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @gpbw-fcop-ui-packages/theme on npm has been identified as a malicious package (version 10.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04728RLUA-2026-05868

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @gpbw-fcop-ui-packages/theme-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