Which versions of internallib_v125 are malicious?

The following npm versions of internallib_v125 are flagged malicious: 1.0.9. Treat any of these as compromised.

How do I remediate internallib_v125 if I installed it?

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

If internallib_v125 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is internallib_v125 part of a known attack campaign?

Yes — internallib_v125 is associated with the GHSA-mfx9-5482-5hjp, RLMA-2025-05398, RLUA-2025-05816 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 internallib_v125 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for internallib_v125 (version 1.0.9).

Malicious package

internallib_v125npm

Advisory published Oct 13, 2025Updated Dec 2, 2025

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

Malicious code in internallib_v125 (npm)

MAL-2025-48324

Immediate action

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

npm uninstall internallib_v125

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

Indicators of compromise (SHA-256)

ab77b49975a46f2335153950e340dc04f11da41aebe8c463f96f99d7e831fff6

dc7e5c242f55ac9cfb19618ea795e6f5e6bcea48fdec85d26eea9de7c1a27408

4c58853ed31046b1876c72dfda01249d2135dd06f329586c8d0dd41dc4b6209f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for internallib_v125 (version 1.0.9).
If you installed it — respond
Remove internallib_v125 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 internallib_v125 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. internallib_v125 on npm has been identified as a malicious package (version 1.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mfx9-5482-5hjpRLMA-2025-05398RLUA-2025-05816

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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