Which versions of orvlla are malicious?

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

How do I remediate orvlla if I installed it?

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

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

Yes — orvlla is associated with the GHSA-554c-89vp-fxq7, RLMA-2025-05466, RLUA-2025-05900, RLUA-2025-06439 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 orvlla 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 orvlla (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging orvlla across your stack and pipelines.

Malicious package

orvllanpm

orvlla is a confirmed malicious npm package (MAL-2025-47947) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in orvlla (npm)

MAL-2025-47947

Immediate action

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

npm uninstall orvlla

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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

56ea7ddcdbe3dab6e4c993804c781fc7cc5d3b48ffc11fea15a0adbee62d9296

ee26b1623c02586a1a88e96bdb630f235ccde8c6d184dd7aa1ebd30fbd46487b

f5573e5890154c59851189a475a3bc4aba294a52e764fa067d5c58dd5a97f896

772e72ff4c0213be40309e2f8495bfb903fa0d89a47c4a8b1a0dffca2b8655d8

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 orvlla (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging orvlla across your stack and pipelines.
If you installed it — respond
Remove orvlla 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 orvlla 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 orvlla 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. orvlla on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-554c-89vp-fxq7RLMA-2025-05466RLUA-2025-05900RLUA-2025-06439

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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