Which versions of oxrvlllcaj are malicious?

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

How do I remediate oxrvlllcaj if I installed it?

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

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

Yes — oxrvlllcaj is associated with the GHSA-f6qc-cc79-w86r, RLMA-2025-05470, RLUA-2025-05903 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 oxrvlllcaj 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 oxrvlllcaj (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 oxrvlllcaj across your stack and pipelines.

Malicious package

oxrvlllcajnpm

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

MAL-2025-47952

Immediate action

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

npm uninstall oxrvlllcaj

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)

be796eae19919fbfc10cbeab99b4560961dd085f2b2d887e64fd81bfaf7f5bbc

48925cddfdee8c5305d7a29237ddc968f723be6934afb33286b2bacb977911c3

4be6a8f3e6ea393d64960fb0983b545d6ff1c52a392433eec7e1de69908ab271

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 oxrvlllcaj (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 oxrvlllcaj across your stack and pipelines.
If you installed it — respond
Remove oxrvlllcaj 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 oxrvlllcaj 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 oxrvlllcaj 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. oxrvlllcaj 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-f6qc-cc79-w86rRLMA-2025-05470RLUA-2025-05903

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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