Which versions of @combinezone/core are malicious?

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

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

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

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

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

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

Malicious package

@combinezone/corenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@combinezone/core is a confirmed malicious npm package (MAL-2026-7061) 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/core (npm)

MAL-2026-7061

Immediate action

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

npm uninstall @combinezone/core

Malicious versions

2 flagged

99.9.999.9.10

Indicators of compromise (SHA-256)

00a0911892c4d31753369979cfcfe35b5d4ccc2194d22b55dc5784132fd1b74e

8428f8033f840b5e9cd5edcfdb50362b5d21534a20b232ff229f135e49388a04

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @combinezone/core (2 malicious versions).
If you installed it — respond
Remove @combinezone/core 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/core 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/core 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-04699RLUA-2026-05843

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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