Which versions of @expue/plugin-express are malicious?

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

How do I remediate @expue/plugin-express if I installed it?

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

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

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

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

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

Malicious package

@expue/plugin-expressnpm

Advisory published Jun 25, 2024Updated Oct 24, 2024

@expue/plugin-express is a confirmed malicious npm package (MAL-2024-2874) 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/plugin-express (npm)

MAL-2024-2874

Immediate action

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

npm uninstall @expue/plugin-express

Malicious versions

1 flagged

0.0.3-alpha.0

Indicators of compromise (SHA-256)

d2ac3e0eca7f60d41c46129a2e9094bf89ed814f6165f61b502881908804b415

0baccdf0fe10d65e874a5bc0483dd29790635eff6dd406187b73f08f80d4ab6f

f731105a2619bfc9f7b838442af523f5410484d353c3bc4720c0c1697da19e63

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @expue/plugin-express (version 0.0.3-alpha.0).
If you installed it — respond
Remove @expue/plugin-express 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/plugin-express 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/plugin-express 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-00065RLUA-2024-05915

Credits

ReversingLabs · finder

Detect & block this

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