Which versions of internallib_v325 are malicious?

Every published version of internallib_v325 on npm is considered malicious. Remove the package entirely.

How do I remediate internallib_v325 if I installed it?

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

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

Yes — internallib_v325 is associated with the GHSA-vvqp-5rpp-x73f 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_v325 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 internallib_v325 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internallib_v325 across your stack and pipelines.

Malicious package

internallib_v325npm

Malicious code in internallib_v325 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-390

Immediate action

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

npm uninstall internallib_v325

What this malware does

The package internallib_v325 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

d5dedf497ea370ca0df69bffd7fd034f3df7e6dfd866e69f3ace19487df89c1e

c291455afc990d6ae2ac49fa20ae7607e6da1a60e5d2ab5d745cfb065c6ca6c8

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

Campaign

GHSA-vvqp-5rpp-x73f

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

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