Which versions of @combinezone/theme are malicious?

The following npm versions of @combinezone/theme are flagged malicious: 99.9.9, 99.9.10. Treat any of these as compromised.

How do I remediate @combinezone/theme if I installed it?

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

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

Yes — @combinezone/theme is associated with the RLMA-2026-04700, RLUA-2026-05844 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 @combinezone/theme across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @combinezone/theme (2 malicious versions).

Malicious package

@combinezone/themenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@combinezone/theme is a confirmed malicious npm package (MAL-2026-7062) that executes malicious code on install (malicious versions 99.9.9, 99.9.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @combinezone/theme (npm)

MAL-2026-7062

Immediate action

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

npm uninstall @combinezone/theme

Malicious versions

2 flagged

99.9.999.9.10

Indicators of compromise (SHA-256)

bf578ea613774de8d01dfd6347ef2efb330fe929af0e0dba4f1d200b18013996

ef2d4c2ae319539a1de7a7c523620e69123be80db6a4e8e5dc6ce1dfe416dfe2

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @combinezone/theme (2 malicious versions).
If you installed it — respond
Remove @combinezone/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 @combinezone/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. @combinezone/theme on npm has been identified as a malicious package (versions 99.9.9, 99.9.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04700RLUA-2026-05844

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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