dtxto1olsnpm
dtxto1ols is a confirmed malicious npm package (MAL-2026-6513) that typosquats a legitimate package to trick installs (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dtxto1ols (npm)
What this malware does
package.json declares a postinstall script that runs automatically on npm install. The script performs filesystem reconnaissance (find / -type f scanning for database client binaries such as mysql and mongo, writing results to /data/db_clients_check.txt) and then POSTs the collected file contents over plaintext HTTP to a Burp Collaborator subdomain at 3dhd6wwmusbh04m22igmzvb4hvnmblza.oastify.com. The destination is an out-of-band attacker-controlled collaborator host with no relationship to the package's advertised string-utility purpose. The package name dtxto1ols also exhibits a digit-1 for letter-l substitution typical of typosquatting, which corroborates malicious intent.
The OpenSSF Package Analysis project identified 'dtxto1ols' @ 1.0.2 (npm) as malicious.
It is considered malicious because:
-
The package communicates with a domain associated with malicious activity.
-
The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dtxto1ols (version 1.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dtxto1ols across your stack and pipelines.
If you installed it — respond
dtxto1ols is a typosquat — you almost certainly intended a legitimately-named package. Remove dtxto1ols, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If dtxto1ols 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 dtxto1ols 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
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks dtxto1ols-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.