Which versions of oxrvxxxxaslllcaj are malicious?

The following npm versions of oxrvxxxxaslllcaj are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate oxrvxxxxaslllcaj if I installed it?

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

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

Yes — oxrvxxxxaslllcaj is associated with the GHSA-gmpp-5qvh-ffw9, RLMA-2025-05475, RLUA-2025-05908 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 oxrvxxxxaslllcaj across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for oxrvxxxxaslllcaj (version 1.0.0).

Malicious package

oxrvxxxxaslllcajnpm

Advisory published Oct 7, 2025Updated Dec 2, 2025

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

Malicious code in oxrvxxxxaslllcaj (npm)

MAL-2025-47958

Immediate action

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

npm uninstall oxrvxxxxaslllcaj

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

ff32d86621f97178147b4ef70b294b280123206967f6341471a6c8bc0893a039

e2b03a01cf7ff6fdf3ea2f23cd669422b2b6a5ad72e4fba1655f171110c08ab4

5b470bae96d995373bc030f2eb15ebe1d5b2c0ffb5c05567af1e6471beb6c50e

Detection & response playbook

Malicious package

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

Campaign

GHSA-gmpp-5qvh-ffw9RLMA-2025-05475RLUA-2025-05908

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks oxrvxxxxaslllcaj-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