MAL-2026-16054 Malicious code in gloggo (npm)
Malicious package
Published
MAL-2026-16054 is a malicious package: gloggo (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-16054/ (Markdown: https://insights.sbomify.com/MAL-2026-16054/index.md)
- Package
- gloggo
- Registry
- npm
What is MAL-2026-16054?
MAL-2026-16054 is a malicious package in gloggo, published on 9 Sep 2026.
Official description
gloggo impersonates the legitimate gulpjs 'glogg' logging library by copying its README, shields, and LICENSE text (attributed to Blaine Bublitz), while package.json attributes authorship to 'Blockvora Team <[email protected]>' with repository 'blockvora/gloggo'. The package name is a one-character variant of 'glogg'. getLogger() invokes isSign('favorite','gloggo',12467) from the dependency 'file-type-detector' and, when that gate returns truthy, executes require('./log'). The './log' module is not present in the tarball, so its bytes must be produced or supplied at require time by the dependency. A logging utility has no legitimate reason to gate its loader on an opaque file-signature check from an unrelated third-party dependency, and the gated path executes code that is not part of the shipped package contents. Consumers who install gloggo believing it to be glogg import a typosquat that conditionally runs code sourced from a suspicious sibling dependency when the module is required.
What should I do about MAL-2026-16054?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.