id79-clientnpm
Advisory published Updated
id79-client is a confirmed malicious npm package (MAL-2026-16173) that steals credentials and exfiltrates sensitive data (malicious version 1.1.79). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in id79-client (npm)
What this malware does
This package is part of a malicious npm campaign published by the biz44 account. Importing the package automatically launches a detached JavaScript loader that retrieves and executes additional code from npoint.io. The retrieved payload communicates with an attacker-controlled server and implements clipboard collection, keyboard and mouse event collection, filesystem scanning, and theft of Chrome extension storage.
On import, index.js calls initialize() which spawns a detached, stdio-suppressed node loader.js child process. loader.js issues an HTTPS GET to https://api.npoint.io/24c12c4b66a29747764f, base64-decodes the code field of the response, and executes it via new Function(require, __dirname, __filename, module, exports, decodedCode) — arbitrary code from a third-party mutable JSON hosting bin runs with full Node privileges on the installer's machine. loader.js additionally monkey-patches Module.prototype.require so any subsequent require('child_process').spawn/execSync call is rewritten to force windowsHide:true and route execSync through a hidden cmd.exe /c spawnSync, ensuring commands issued by the remotely fetched payload run invisibly on Windows. The detached-and-unref'd child, suppressed stdio, and stealth child_process wrapper are consistent with a persistent covert loader whose actual behavior is controlled by whoever owns the npoint bin.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for id79-client (version 1.1.79).
If you installed it — respond
id79-client is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If id79-client was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
Credits
- Amazon Inspector · finder
- ESTsecurity · finder
- pkgwarden · finder
Detect & block this
O3 blocks id79-client-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.