Which versions of ro-mobile are malicious?

The following npm versions of ro-mobile are flagged malicious: 999.0.0, 999.0.1. Treat any of these as compromised.

How do I remediate ro-mobile if I installed it?

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

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

Yes — ro-mobile is associated with the GHSA-85m3-w425-6v48, RLMA-2026-01541 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 ro-mobile 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 ro-mobile (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ro-mobile across your stack and pipelines.

Malicious package

ro-mobilenpm

Malicious code in ro-mobile (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192698

Immediate action

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

npm uninstall ro-mobile

What this malware does

The package ro-mobile was found to contain malicious code.

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

999.0.0999.0.1

Indicators of compromise (SHA-256)

ba9c94a8695242e09289eca1f734da5c96b789f911e1e1cbc6a7279486dfb36d

9720efd6aba66e7a6a07c30debc177402cf521360448144f8804370656d64b88

e7fd5c50dc36953ddeb509d6b53c7f8c19c502c35d40b95adee547d46fc59b10

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

Campaign

GHSA-85m3-w425-6v48RLMA-2026-01541

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ro-mobile-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