Which versions of @expue/core are malicious?

The following npm versions of @expue/core are flagged malicious: 0.0.3-alpha.0. Treat any of these as compromised.

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

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

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

Yes — @expue/core is associated with the RLMA-2024-00064, RLUA-2024-05914 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 @expue/core across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @expue/core (version 0.0.3-alpha.0).

Part of a larger attack: @expue published 11 malicious packages. See the full campaign →

Malicious package

@expue/corenpm

Advisory published Jun 25, 2024Updated Oct 24, 2024

@expue/core is a confirmed malicious npm package (MAL-2024-7073) that executes malicious code on install (malicious version 0.0.3-alpha.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @expue/core (npm)

MAL-2024-7073

Immediate action

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

npm uninstall @expue/core

Malicious versions

1 flagged

0.0.3-alpha.0

Indicators of compromise (SHA-256)

0509af6ef4edaf92861ec0d67cf56206eae53f631cc8598ca67eb2d2de354cad

961cf465eac59416e0ffb999aad6876cde7e0e6f7818e0061c17b67a73bc50e6

bdef0d24a2521eacdeb9af80869a580008abd9e21e56b69ee233b8e99c55c11c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @expue/core (version 0.0.3-alpha.0).
If you installed it — respond
Remove @expue/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 @expue/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. @expue/core on npm has been identified as a malicious package (version 0.0.3-alpha.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-00064RLUA-2024-05914

Credits

ReversingLabs · finder

Detect & block this

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