Which versions of ballance-check are malicious?

The following npm versions of ballance-check are flagged malicious: 1.2.6. Treat any of these as compromised.

How do I remediate ballance-check if I installed it?

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

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

Yes — ballance-check is associated with the GHSA-rvcw-vr6m-ghqm, RLMA-2025-05285, RLUA-2025-05690 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 ballance-check 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 ballance-check (version 1.2.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ballance-check across your stack and pipelines.

Malicious package

ballance-checknpm

ballance-check is a confirmed malicious npm package (MAL-2025-47973) that executes malicious code on install (malicious version 1.2.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ballance-check (npm)

MAL-2025-47973

Immediate action

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

npm uninstall ballance-check

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.2.6

Indicators of compromise (SHA-256)

9d2685c68a4c8516f69c39001102234d71d9fdb43a4c2b23ae83242808d9c3b1

c0f93eed6a2ee56c7162e78c8f908421455ed0a88a3000f82f12eb7f760560e6

43077e45ed95edddfbcaa5141252650d1ba995a95ad808c66e88a1bda2746c84

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

Campaign

GHSA-rvcw-vr6m-ghqmRLMA-2025-05285RLUA-2025-05690

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ballance-check-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