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

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

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

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

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

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

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

Malicious package

@xp-utilities/utilitiesnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@xp-utilities/utilities is a confirmed malicious npm package (MAL-2026-7103) 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/utilities (npm)

MAL-2026-7103

Immediate action

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

npm uninstall @xp-utilities/utilities

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

4f2a5f0a21d1406750798ea153d3206f6b45a837f9fd747b44f9b54dec84b190

e729e76140efd50261be4a5e32e5ebc81864f39f7c1f0f364419b94398c03e40

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @xp-utilities/utilities (version 99.0.0).
If you installed it — respond
Remove @xp-utilities/utilities 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/utilities 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/utilities 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-04815RLUA-2026-05946

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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