Which versions of @expue/builder are malicious?

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

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

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

If @expue/builder was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @expue/builder part of a known attack campaign?

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @expue/builder (version 0.0.3-alpha.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @expue/builder across your stack and pipelines.

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

Malicious package

@expue/buildernpm

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

MAL-2024-1843

Immediate action

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

npm uninstall @expue/builder

Malicious versions

1 flagged

0.0.3-alpha.0

Indicators of compromise (SHA-256)

7956416a73ed6511ca07d5d2166b864d31785ea6b663b074a9bd025b85fbfbf4

993e36b1bfc147d9275742d40131c47c0b49e8d5829124bb0d18e98479a1ed11

f60936d0961d377d94460d5278e8b6b73bb2a416e63f59b88ce58385577f3434

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @expue/builder (version 0.0.3-alpha.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @expue/builder across your stack and pipelines.
If you installed it — respond
Remove @expue/builder 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/builder was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @expue/builder before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @expue/builder 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-00061RLUA-2024-05911

References

Credits

ReversingLabs · finder

Detect & block this

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