Which versions of base62-58x are malicious?

The following npm versions of base62-58x are flagged malicious: 5.0.1, 5.0.2. Treat any of these as compromised.

How do I remediate base62-58x if I installed it?

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

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

Yes — base62-58x is associated with the GHSA-35vp-3qxv-xfp5, RLMA-2025-05691, RLUA-2025-06065 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 base62-58x 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 base62-58x (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging base62-58x across your stack and pipelines.

Malicious package

base62-58xnpm

Malicious code in base62-58x (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190624

Immediate action

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

npm uninstall base62-58x

What this malware does

The package base62-58x 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

5.0.15.0.2

Indicators of compromise (SHA-256)

5cd641e4e74a586087038295a99f8a1ee51c4b8ee02dd79da6aec94e39c39999

329e19a0dfe372f18c65552e38f92a7cdaeae2c3bcfae8956d0a233a7885da88

0fda945f06a36c77ba571ea3f33407a35bb007a76009ab1eae66d54d4e64c139

0d50b3c18ac73ef31fe2e87447896b1d03a8adcca8a7a164359f83124a903f02

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

Campaign

GHSA-35vp-3qxv-xfp5RLMA-2025-05691RLUA-2025-06065

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks base62-58x-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