Malicious code in ach-detail (npm)
The npm package ach-detail@99.0.1 contains a malicious preinstall script that exfiltrates system information (hostname, Node.js version, platform, timestamp) to a remote endpoint. The version-inflation pattern suggests dependency-confusion targeting of a private internal package.
- Disclosed
- Last updated
- Blast radius
- Public npm registry; any user installing ach-detail@99.0.1 would execute the malicious preinstall script.
- Ecosystems
- Attack vectors
- Affected entities
- ach-detail · 99.0.1
The npm package ach-detail version 99.0.1 was published to the public npm registry containing a preinstall lifecycle script (scripts/preinstall.js) that executes automatically during npm install. The script collects sensitive installer metadata including hostname, package name and version, Node.js version, platform, timestamp, and a nonce, then POSTs this data to a hardcoded remote endpoint at https://callback.kuldeep.io/beacon with an HTTP fallback to the same host.
The use of version 99.0.1—a version-inflation pattern—is consistent with dependency-confusion attacks targeting a private internal package of the same name. An attacker publishing to the public registry with an artificially high version number can intercept installations from systems that resolve the public package instead of the intended private one.
The script contains a log string self-labeling the behavior as an authorized bug-bounty proof-of-concept, but this label is author-controlled and does not represent actual consent from package installers. The exfiltration of host identifiers to a non-first-party endpoint poses a direct risk to any system that installs this version.
This incident was identified and credited to the OpenSSF malicious-packages project.
Indicators of compromise
- Packages
- ach-detail@99.0.1
- Domains
- callback.kuldeep.io
Remediation
- Immediately uninstall ach-detail@99.0.1 from all systems and projects
- Audit npm install logs to identify any systems that installed this version
- Review network logs for outbound connections to callback.kuldeep.io
- Update to a safe version of ach-detail if a legitimate version exists, or remove the dependency entirely
- Consider using npm audit to detect any remaining installations of this malicious version
- Implement dependency-confusion protections such as npm scopes or private registry configuration to prevent similar attacks
Sources
- GitHub Advisory GHSA-j5q4-grmc-8327 · GitHub Advisory Database
Cite this entry
"Malicious code in ach-detail (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 7, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-ach-detail-npm-f4dak4
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in depcruise-wrap-stream-in-html (npm)
depcruise-wrap-stream-in-html@99.9.1 is a malicious npm package that mimics an internal helper of dependency-cruiser. It is a hollow package that downloads and executes arbitrary code from a Google Cloud Storage bucket during installation.
npmCompromised packageDependency confusionTyposquatting - containedcritical
Malicious code in akamaijs-sensor (npm)
The npm package akamaijs-sensor contained malicious code that executed arbitrary JavaScript via hidden Unicode-encoded bytes and established a command-and-control channel through a Google Calendar dead-drop. The package was designed to run attacker-authored code in the consumer's Node process when the sensor() API was called.
npmCompromised packageMalicious commit - containedcritical
Malicious code in gunzip-js (npm)
The npm package gunzip-js version 99.9.1 was identified as malicious by the OpenSSF Package Analysis project. The malicious version communicates with a domain associated with malicious activity.
npmCompromised package - resolvedcritical
Malicious code in @velliajs/discord (npm)
@velliajs/discord, a malicious npm package masquerading as a discord.js clone, contained two hostile mechanisms: an unpinned private git dependency with embedded GitHub PAT enabling arbitrary code injection on install, and a hidden runtime kill-switch that gates bot functionality based on a remote allow-list. Two live GitHub Personal Access Tokens were hardcoded in the package.
npmCompromised packageMalicious commit