MalwarePublished 28 Oct 2025Updated 31 Oct 2025

internallib_v799 (npm) · Malicious Code

Affects internallib_v799Source GCVE Database

Malicious package : remove internallib_v799 and rotate any secrets on hosts that installed it.

Data as of 29 Oct 2026, 23:24 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-48931

What to do

Remove internallib_v799 from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npminternallib_v799	Affected–	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package internallib_v799 was identified as containing malicious code. Any system with this package installed or running is considered fully compromised, with the potential for complete control by an outside entity. Immediate removal of the package is recommended, but it may not fully eliminate the malicious presence. All secrets and keys on the affected system should be rotated from a different, uncompromised machine.

Impact

Systems with the internallib_v799 package installed are fully compromised, potentially allowing attackers complete control. Sensitive information such as secrets and keys stored on the affected machines are exposed and must be rotated. The malicious code may persist beyond the removal of the package, indicating a deep compromise.

Defensive guidance

Remove the internallib_v799 package immediately from affected systems. Rotate all secrets and keys stored on the compromised machines from a different, secure computer. Due to the likelihood of persistent compromise, consider rebuilding or thoroughly cleaning the affected systems to ensure removal of all malicious components.

Summary

The internallib_v799 npm package has been found to include malicious code that compromises any computer on which it is installed or executed. According to the source details, the compromise is severe enough to consider the system fully controlled by an attacker. The malicious package presence implies that secrets and keys stored on the system are at risk and must be rotated immediately from a secure environment. Removal of the package alone does not guarantee the eradication of all malicious software introduced by it.

References

github.com/advisories/GHSA-w298-79mv-2mm6 (opens in a new tab)

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 23:24 UTC

Technical details

References

Community reviews