Which versions of ach-detail are malicious?

The following npm versions of ach-detail are flagged malicious: 99.0.1, 99.0.2. Treat any of these as compromised.

How do I remediate ach-detail if I installed it?

ach-detail establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed ach-detail — how do I know if it already compromised me?

If ach-detail was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is ach-detail part of a known attack campaign?

Yes — ach-detail is associated with the IN-MAL-2026-014873, IN-MAL-2026-016674 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ach-detail across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ach-detail (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ach-detail across your stack and pipelines.

Malicious package

ach-detailnpm

ach-detail is a confirmed malicious npm package (MAL-2026-12334) that opens a backdoor for remote access (malicious versions 99.0.1, 99.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ach-detail (npm)

MAL-2026-12334

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall ach-detail

What this malware does

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.

Malicious versions

2 flagged

99.0.199.0.2

Indicators of compromise (SHA-256)

136c9cd3535c5ebb047f79bd6de88016db816903f1623cf96b5e765c78cab97e

6c8ce91cbe1aaa587613795b1b82cc84384b499a29af4a18c0a820b77ea1d834

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ach-detail (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ach-detail across your stack and pipelines.
If you installed it — respond
ach-detail establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If ach-detail was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ach-detail before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. ach-detail on npm has been identified as a malicious package (versions 99.0.1, 99.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014873IN-MAL-2026-016674

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ach-detail-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database