Which versions of oxrvxalllcaj are malicious?

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

How do I remediate oxrvxalllcaj if I installed it?

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

If oxrvxalllcaj was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is oxrvxalllcaj part of a known attack campaign?

Yes — oxrvxalllcaj is associated with the GHSA-9h8m-2x89-h2wc, RLMA-2025-05471, RLUA-2025-05904 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 oxrvxalllcaj across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for oxrvxalllcaj (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging oxrvxalllcaj across your stack and pipelines.

Malicious package

oxrvxalllcajnpm

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

MAL-2025-47953

Immediate action

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

npm uninstall oxrvxalllcaj

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)

c188f8718a360fffb7f5a032f1b21e428c2fc9542ab537b0acd0c602b28d3a0c

29bcd4bbaa76e2cb09865b17e45b86432964cd187ab16a1a6ce38ac05e013061

1a2452ebb209830dbddcf9ef7ebd0516037b67d4eb3d8236278a1517bb2be1bd

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for oxrvxalllcaj (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging oxrvxalllcaj across your stack and pipelines.
If you installed it — respond
Remove oxrvxalllcaj 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 oxrvxalllcaj was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks oxrvxalllcaj before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. oxrvxalllcaj 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-9h8m-2x89-h2wcRLMA-2025-05471RLUA-2025-05904

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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