MalwarePublished 9 Sep 2026Updated 11 Nov 2026

gloggo (npm) · Malicious Code

Affects gloggoSource GCVE Database

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

Data as of 11 Nov 2026, 17:36 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-16054

What to do

Remove gloggo 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
npmgloggo	Affected =1.1.3 =1.1.4 =1.1.2	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 'gloggo' is a malicious typosquatting variant of the legitimate 'glogg' logging library. It impersonates 'glogg' by copying its README, shields, and license text but attributes authorship to a suspicious entity. The package conditionally executes code from a dependency that is not part of the shipped package, which is unusual for a logging utility. Installation of 'gloggo' can lead to full system compromise, requiring immediate secret and key rotation and package removal.

Impact

Systems with 'gloggo' installed are considered fully compromised. The package can execute arbitrary code not included in the original package, potentially allowing attackers full control over the affected system. All secrets and keys stored on the compromised system should be rotated immediately from a secure environment. Removing the package alone may not fully remediate the compromise due to potential persistence mechanisms.

Defensive guidance

Remove the 'gloggo' package immediately from all affected systems. Rotate all secrets and keys stored on compromised systems from a separate, secure device. Due to the high likelihood of full system compromise, conduct a thorough investigation and consider rebuilding affected systems.

Summary

The 'gloggo' npm package is a typosquatting malware that mimics the legitimate 'glogg' logging library. It copies documentation and license content from 'glogg' but is authored by 'Blockvora Team'. The package's getLogger() function calls a gate function from a dependency 'file-type-detector' and conditionally executes code from a './log' module that is not included in the package tarball, implying code is supplied at runtime by the dependency. This behavior is suspicious and indicates malicious intent. Systems with this package installed should be considered fully compromised.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 17:36 UTC

Technical details

References

Community reviews