Which versions of oxrvxxaslllcaj are malicious?

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

How do I remediate oxrvxxaslllcaj if I installed it?

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

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

Yes — oxrvxxaslllcaj is associated with the GHSA-2g33-w92h-4wm6, RLMA-2025-05473, RLUA-2025-05906 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 oxrvxxaslllcaj across my projects, lockfiles, and CI pipelines?

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

Malicious package

oxrvxxaslllcajnpm

Advisory published Oct 7, 2025Updated Dec 2, 2025

oxrvxxaslllcaj is a confirmed malicious npm package (MAL-2025-47956) 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 oxrvxxaslllcaj (npm)

MAL-2025-47956

Immediate action

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

npm uninstall oxrvxxaslllcaj

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)

c8e27b404d616eeff51c5068a177cef1eb09921210572e1451774382c390bf05

9db5c622e4353bcdb8565e8633fa9502c21c300cb00e53820e3fbbfc33492f1a

12c300806e8d85987a271c88020a2c2b4dcda0bc712a1f7cdee1f029b1eb4b1b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for oxrvxxaslllcaj (version 1.0.0).
If you installed it — respond
Remove oxrvxxaslllcaj 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 oxrvxxaslllcaj 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. oxrvxxaslllcaj 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-2g33-w92h-4wm6RLMA-2025-05473RLUA-2025-05906

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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