MalwarePublished 13 Jul 2026

sixseven8 (npm) · Malicious Code

Affects sixseven8Source GCVE Database

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

Data as of 26 Oct 2026, 15:56 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-10380

What to do

Remove sixseven8 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
npmsixseven8	Affected =1.7.7	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 'sixseven8' contains malicious code that compromises any computer on which it is installed or running. Installation of this package can lead to full system compromise, including unauthorized access to secrets and keys stored on the affected machine. Simply removing the package may not fully eliminate the malicious presence, as attackers may have established persistent control.

Impact

Systems with the 'sixseven8' package installed are at risk of full compromise, including unauthorized access to stored secrets and keys. This can lead to significant security breaches, data loss, and potential lateral movement within affected environments. The persistence of malicious code beyond package removal increases the risk and complexity of remediation.

Defensive guidance

Remove the 'sixseven8' package immediately from all affected systems. Consider any system with this package installed as fully compromised. Rotate all secrets and keys stored on the compromised machines from a separate, secure system. Conduct a thorough investigation and remediation to identify and remove any persistent malicious components beyond the package itself.

Summary

The 'sixseven8' package in the npm ecosystem is identified as containing malicious code. According to the source advisory, any system with this package installed should be considered fully compromised. Attackers may have gained full control over the system, potentially accessing sensitive information such as secrets and keys. Removal of the package alone does not guarantee eradication of the malicious software introduced. Immediate rotation of all secrets and keys from a separate, uncompromised system is strongly advised.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Jul 2026, 09:35 UTC

Technical details

References

Community reviews