Which versions of @xp-utilities/web are malicious?

The following npm versions of @xp-utilities/web are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate @xp-utilities/web if I installed it?

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

If @xp-utilities/web 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 @xp-utilities/web part of a known attack campaign?

Yes — @xp-utilities/web is associated with the RLMA-2026-04816, RLUA-2026-05947 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 @xp-utilities/web across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @xp-utilities/web (version 99.0.0).

Malicious package

@xp-utilities/webnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@xp-utilities/web is a confirmed malicious npm package (MAL-2026-7104) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @xp-utilities/web (npm)

MAL-2026-7104

Immediate action

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

npm uninstall @xp-utilities/web

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

d539cf8ba2f6c588aaa837c154825da4325ab71e54494fc01af5de9a3c3db527

7788d348ece90b0f74ba007286be8d560e3a6c13d45b37f6798b3f6ebc3c5b2a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04816RLUA-2026-05947

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @xp-utilities/web-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