MAL-2026-18460
Malicious code in dependencykfee-2 (npm)
Auswirkung
The package ships only a package.json with description 'test', an empty dependencies list, a declared main (index.js) that is not present in the tarball, and config.unsafe-perm set to true. Its preinstall lifecycle script runs a node one-liner that hex-encodes process.cwd(), splits the hex into DNS-label-sized chunks, and issues a dns.lookup against <hex-chunks>.google.com. On npm install, this emits the installer's current working directory path (which typically reveals the OS username, host layout, and project name) as a DNS query, where passive DNS collectors and the authoritative resolver on the attacker-controlled suffix can harvest it. The google.com suffix is used as cover; the exfiltrated content is encoded into the subdomain labels. The package provides no advertised functionality — the entire shipped payload is the install-time beacon, consistent with a dependency-confusion / reconnaissance probe. The OpenSSF Package Analysis project identified 'dependencykfee-2' @ 1.0.0 (npm) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.
Betroffene Pakete
| Ökosystem | Paket | Betroffen | Behoben in |
|---|---|---|---|
| npm | dependencykfee-2 | unbekannt | nicht erfasst |