Which versions of orvllaa are malicious?

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

How do I remediate orvllaa if I installed it?

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

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

Yes — orvllaa is associated with the GHSA-w4gx-qg6h-26j2, RLMA-2025-05467, RLUA-2025-05901 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 orvllaa 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 orvllaa (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 orvllaa across your stack and pipelines.

Malicious package

orvllaanpm

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

MAL-2025-47948

Immediate action

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

npm uninstall orvllaa

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)

c14485f093ca8dc9ed7f8edb235eac174df0118b3960643c3c0c8ddc8d2bf7aa

5ca0b5d73f868c84d83a03a56f744c3c09b323cf89c2fea9ed08badb8fa36a36

f85ddf1a1af182e6d47bef319c1cb72f442d90d89fda6c3b1661895e31a603f5

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 orvllaa (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 orvllaa across your stack and pipelines.
If you installed it — respond
Remove orvllaa 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 orvllaa 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 orvllaa 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. orvllaa 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-w4gx-qg6h-26j2RLMA-2025-05467RLUA-2025-05901

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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