Which versions of oxrvxxxxxaslllcaj are malicious?

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

How do I remediate oxrvxxxxxaslllcaj if I installed it?

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

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

Yes — oxrvxxxxxaslllcaj is associated with the GHSA-4rcv-g652-28v2, RLMA-2025-05476, RLUA-2025-05909 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 oxrvxxxxxaslllcaj 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 oxrvxxxxxaslllcaj (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 oxrvxxxxxaslllcaj across your stack and pipelines.

Malicious package

oxrvxxxxxaslllcajnpm

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

MAL-2025-47959

Immediate action

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

npm uninstall oxrvxxxxxaslllcaj

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)

cbb43c3aa5e1fe9b33fc7a3c3a439ef7edd69817df8984551602b834f7b64584

9c56fa5117029413824f14703f8bbc872d9fdecd9af61b65496f48897966ee0d

bd0425f4de18f88a16b1ee42a6ecb995d42f74b683d856aa8f17764de15fdf74

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 oxrvxxxxxaslllcaj (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 oxrvxxxxxaslllcaj across your stack and pipelines.
If you installed it — respond
Remove oxrvxxxxxaslllcaj 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 oxrvxxxxxaslllcaj 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 oxrvxxxxxaslllcaj 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. oxrvxxxxxaslllcaj 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-4rcv-g652-28v2RLMA-2025-05476RLUA-2025-05909

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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