Malicious code in ach-detail (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (6c8ce91cbe1aaa587613795b1b82cc84384b499a29af4a18c0a820b77ea1d834) The npm package [email protected] ships a preinstall lifecycle script (scripts/preinstall.js) that runs automatically on `npm install`. The script collects the installer's hostname, package name and version, Node.js version, platform, timestamp, and a nonce, and POSTs the payload to a hardcoded remote endpoint at https://callback.kuldeep.io/beacon, with an HTTP fallback to the same host. The package is published to the public npm registry at version 99.0.1 — a version-inflation pattern consistent with dependency-confusion targeting of a private internal package of the same name. A log string in the script self-labels the behavior as an authorized bug-bounty PoC, but that label is author-controlled, does not change the observable behavior, and does not represent consent from any installer that resolves the package (accidentally or through dependency-confusion). Installer-side host identifiers leave the machine to a non-first-party endpoint on install.
AI Analysis
Technical Summary
The 'ach-detail' npm package version 99.0.2 includes a malicious preinstall.js script that runs automatically during npm install. It gathers host system identifiers such as os.hostname(), OS type/version/release, CPU architecture, output of 'whoami', non-internal IPv4 addresses, Node.js version, and package identity. This information is sent as a JSON payload to a hardcoded endpoint at https://callback.kuldeep.io/beacon, with an insecure HTTP fallback if HTTPS fails. The endpoint is not configurable by the installer, and the installer does not opt in to this data collection. The fallback to plaintext HTTP exposes the collected data to network interception. The script's self-labeling as a proof-of-concept or bug bounty placeholder is controlled by the package author and does not imply installer consent.
Potential Impact
Sensitive host information is exfiltrated without user consent, potentially exposing system identity, user information, network details, and environment specifics to an attacker-controlled server. The fallback to plaintext HTTP further risks interception of this data by network attackers. This compromises user privacy and may aid further targeted attacks or reconnaissance.
Mitigation Recommendations
No official patch or remediation is currently available. Users should avoid installing version 99.0.2 of the 'ach-detail' package. Monitor vendor advisories for updates or patches. Consider auditing npm packages before installation to detect unauthorized scripts.
Malicious code in ach-detail (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (6c8ce91cbe1aaa587613795b1b82cc84384b499a29af4a18c0a820b77ea1d834) The npm package [email protected] ships a preinstall lifecycle script (scripts/preinstall.js) that runs automatically on `npm install`. The script collects the installer's hostname, package name and version, Node.js version, platform, timestamp, and a nonce, and POSTs the payload to a hardcoded remote endpoint at https://callback.kuldeep.io/beacon, with an HTTP fallback to the same host. The package is published to the public npm registry at version 99.0.1 — a version-inflation pattern consistent with dependency-confusion targeting of a private internal package of the same name. A log string in the script self-labels the behavior as an authorized bug-bounty PoC, but that label is author-controlled, does not change the observable behavior, and does not represent consent from any installer that resolves the package (accidentally or through dependency-confusion). Installer-side host identifiers leave the machine to a non-first-party endpoint on install.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The 'ach-detail' npm package version 99.0.2 includes a malicious preinstall.js script that runs automatically during npm install. It gathers host system identifiers such as os.hostname(), OS type/version/release, CPU architecture, output of 'whoami', non-internal IPv4 addresses, Node.js version, and package identity. This information is sent as a JSON payload to a hardcoded endpoint at https://callback.kuldeep.io/beacon, with an insecure HTTP fallback if HTTPS fails. The endpoint is not configurable by the installer, and the installer does not opt in to this data collection. The fallback to plaintext HTTP exposes the collected data to network interception. The script's self-labeling as a proof-of-concept or bug bounty placeholder is controlled by the package author and does not imply installer consent.
Potential Impact
Sensitive host information is exfiltrated without user consent, potentially exposing system identity, user information, network details, and environment specifics to an attacker-controlled server. The fallback to plaintext HTTP further risks interception of this data by network attackers. This compromises user privacy and may aid further targeted attacks or reconnaissance.
Mitigation Recommendations
No official patch or remediation is currently available. Users should avoid installing version 99.0.2 of the 'ach-detail' package. Monitor vendor advisories for updates or patches. Consider auditing npm packages before installation to detect unauthorized scripts.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12334
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a735743bf8831d539159bf5
Added to database: 08/05/2026, 15:31:15 UTC
Last enriched: 08/05/2026, 17:13:59 UTC
Last updated: 09/07/2026, 22:21:37 UTC
Views: 19
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.