Which versions of oxrvxxxaslllcaj are malicious?

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

How do I remediate oxrvxxxaslllcaj if I installed it?

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

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

Yes — oxrvxxxaslllcaj is associated with the GHSA-jx5h-6w34-cq76, RLMA-2025-05474, RLUA-2025-05907 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 oxrvxxxaslllcaj 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 oxrvxxxaslllcaj (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 oxrvxxxaslllcaj across your stack and pipelines.

Malicious package

oxrvxxxaslllcajnpm

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

MAL-2025-47957

Immediate action

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

npm uninstall oxrvxxxaslllcaj

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)

9121764b98e89489abb502bcc35fb1b4cd7c34e64216932ba31a3b908a1e12a9

8570a53f81b68055022b1edc4304132cff79935319c6cc71e9d39708e8615a22

9e86683ec6c832aaf8f1c8665540020ff6557ae018cbee9bcb2b7ff6025d20ce

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 oxrvxxxaslllcaj (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 oxrvxxxaslllcaj across your stack and pipelines.
If you installed it — respond
Remove oxrvxxxaslllcaj 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 oxrvxxxaslllcaj 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 oxrvxxxaslllcaj 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. oxrvxxxaslllcaj 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-jx5h-6w34-cq76RLMA-2025-05474RLUA-2025-05907

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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