Which versions of express-xmlrequest are malicious?

The following npm versions of express-xmlrequest are flagged malicious: 2.2.8. Treat any of these as compromised.

How do I remediate express-xmlrequest if I installed it?

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

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

Yes — express-xmlrequest is associated with the RLMA-2025-05011, RLUA-2025-05793 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 express-xmlrequest across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for express-xmlrequest (version 2.2.8).

Malicious package

express-xmlrequestnpm

Advisory published Sep 26, 2025Updated Dec 2, 2025

express-xmlrequest is a confirmed malicious npm package (MAL-2025-47669) that executes malicious code on install (malicious version 2.2.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in express-xmlrequest (npm)

MAL-2025-47669

Immediate action

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

npm uninstall express-xmlrequest

Malicious versions

1 flagged

2.2.8

Indicators of compromise (SHA-256)

167762921e226f8fc6d60948da5d6fbb43247ef0b89ff4133837841b5eabc8a1

a5e6ed159226211de616785972648a6c7656cb72310ea920e22ae22d1d849c18

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05011RLUA-2025-05793

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks express-xmlrequest-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