MalwarePublished 9 Sep 2026Updated 11 Nov 2026

file-type-detector (npm) · Malicious Code

Affects file-type-detectorSource GCVE Database

Malicious package : remove file-type-detector 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-16053

What to do

Remove file-type-detector 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
npmfile-type-detector	Affected =1.1.0 =1.1.1	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 file-type-detector versions 1.1.0 and 1.1.1 contain malicious code that writes a payload to a sibling package's log file and enables execution of that payload through a chain of dependencies. This results in full compromise of any computer running or having installed these versions. Immediate removal and secret/key rotation are strongly advised.

Impact

Any system with file-type-detector versions 1.1.0 or 1.1.1 installed or running is considered fully compromised. Attackers may have gained full control, potentially accessing all secrets and keys stored on the system. Removal of the package alone does not guarantee eradication of the malicious presence. Immediate rotation of all secrets and keys from a separate, trusted system is necessary to mitigate ongoing risk.

Defensive guidance

Remove the file-type-detector package versions 1.1.0 and 1.1.1 immediately. Rotate all secrets and keys from a different, uncompromised computer. Due to the full compromise risk, assume that the affected system is untrusted and perform a thorough incident response.

Summary

The file-type-detector package (versions 1.1.0 and 1.1.1) is a clone of file-type-checker with an added undocumented function isSign that writes a malicious payload to a sibling package's log file. This payload is then executed by the gloggo package (versions 1.1.2 to 1.1.4) via require(), which is triggered by the sonmors package (a typosquat of sonner). The malicious chain is triggered upon requiring gloggo, with no install hooks involved. The npm publisher log-developer published gloggo and file-type-detector within five minutes on 2026-08-27. The malicious code allows full compromise of affected systems, with silent failure on errors to evade detection.

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