Which versions of mobile-international are malicious?

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

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

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

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

Yes — mobile-international is associated with the GHSA-f4h6-f7mh-jhjh, RLMA-2026-05161 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 mobile-international 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 mobile-international (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mobile-international across your stack and pipelines.

Malicious package

mobile-internationalnpm

mobile-international is a confirmed malicious npm package (MAL-2026-4320) that executes malicious code on install (malicious version 999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mobile-international (npm)

MAL-2026-4320

Immediate action

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

npm uninstall mobile-international

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

999.0.0

Indicators of compromise (SHA-256)

543efd73c4d2860379f7e412db8f3ddb33401c3788a2a18f5ec0648e33b51a33

a3bafffdec211ea172cd9bccf362a3375f1f91853a84bcf28cc16f8b20e79365

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

Campaign

GHSA-f4h6-f7mh-jhjhRLMA-2026-05161

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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