Which versions of oxrvxaslllcaj are malicious?

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

How do I remediate oxrvxaslllcaj if I installed it?

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

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

Yes — oxrvxaslllcaj is associated with the GHSA-44fq-pj73-pqh8, RLMA-2025-05472, RLUA-2025-05905 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 oxrvxaslllcaj 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 oxrvxaslllcaj (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 oxrvxaslllcaj across your stack and pipelines.

Malicious package

oxrvxaslllcajnpm

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

MAL-2025-47954

Immediate action

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

npm uninstall oxrvxaslllcaj

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)

2ca07bc07dea87a05077e44cc62e1e153cd9d75fd15fd02382ffc42266d072e9

3b887852d23bf3be2068346da70ca49303ca5bf3b21cdbd528cbd00faa4e16bf

56fb96f8fb42f7ee06fe8ada306d39d45d154db304977d03947a4ce0f2f541c7

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 oxrvxaslllcaj (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 oxrvxaslllcaj across your stack and pipelines.
If you installed it — respond
Remove oxrvxaslllcaj 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 oxrvxaslllcaj 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 oxrvxaslllcaj 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. oxrvxaslllcaj 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-44fq-pj73-pqh8RLMA-2025-05472RLUA-2025-05905

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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