Which versions of ixpresso-core are malicious?

The following npm versions of ixpresso-core are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate ixpresso-core if I installed it?

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

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

Yes — ixpresso-core is associated with the RLMA-2026-05120, RLUA-2026-06288 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 ixpresso-core across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ixpresso-core (3 malicious versions).

Malicious package

ixpresso-corenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

ixpresso-core is a confirmed malicious npm package (MAL-2026-7304) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ixpresso-core (npm)

MAL-2026-7304

Immediate action

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

npm uninstall ixpresso-core

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

0ba2d319fe6d6ce25abf161a27a869394f6ca32e4a5de0179f5b88fb5d1e90f8

357ecc50b23eba787849d514f08f2892f67e8dc9141be3502c2ab57edc50eaf1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ixpresso-core (3 malicious versions).
If you installed it — respond
Remove ixpresso-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 ixpresso-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. ixpresso-core on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05120RLUA-2026-06288

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks ixpresso-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