LWA-2026-13477 confirmed malware

dependencykfeg@25.2.1

Malicious code in dependencykfeg (npm)

T1195.002 · Compromise Software Supply ChainT1105 · Ingress Tool Transfer

Analysis

dependencykfeg@25.2.1 is a manifest-only npm package (a single package.json, 346 bytes unpacked, no JavaScript, no lifecycle scripts, no bin entries) whose entire function is to make npm install fetch code from outside the registry. Its dependencies block declares node-acct-utilssss21 pointing directly at a raw GitHub tarball, hxxps://github[.]com/GamerD11/ping_test/raw/refs/heads/main/node-acct-utils-1[.]0[.]0[.]tgz, so `npm install dependencykfeg` downloads and unpacks that externally hosted archive and runs whatever install scripts it contains, bypassing registry provenance, integrity metadata and audit trail. The package also lists itself as its own dependency (dependencykfeg: ^25.1.3), which makes the installer re-resolve and re-install the package inside its own tree — a redirection used to hide the external fetch among ordinary install output, and one that confuses private registry mirrors. The dependency name node-acct-utilssss21 is a combosquat of node-acct-utils carrying the real name intact with a padded suffix, chosen to look like a plausible helper library. The code that actually executes is not in this tarball: it is delivered by the GitHub-hosted archive, and the tarball's payload should be treated as unknown; the package itself contributes only the loader directive. Earlier versions of the same package name were also malicious, so any version of dependencykfeg should be removed and npm cache/registry mirrors checked for the fetched tarball.

analyzed by
Leitwacht
first seen
Oct 30, 2026, 06:36 AM
analyzed
Oct 30, 2026, 07:05 AM

Related advisories

browse all confirmed advisories →

Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.