ts-anklenpm
Advisory published Updated
ts-ankle is a confirmed malicious npm package (MAL-2026-6548) that steals credentials and exfiltrates sensitive data (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ts-ankle (npm)
What this malware does
On npm install, [email protected] runs a postinstall hook (node test.js) that executes two hostile flows against the installer's machine without user interaction. (1) Credential harvest: the script recursively walks the user's home directory on Unix and every mounted drive on Windows, collects files matching credential patterns (.env, .json, .toml, .pem, id.json, etc.), and POSTs them as multipart form uploads to https://datasecure-service.vercel.app/api/v1. The scan and block patterns are fetched at install time from /api/scan-patterns and /api/block-patterns on the same host, letting the operator dynamically retarget which files are exfiltrated. (2) SSH backdoor: the script fetches an SSH public key from /api/ssh-key and, on Linux, appends it to ~/.ssh/authorized_keys, chowns the directory via sudo, and runs sudo ufw enable + sudo ufw allow 22/tcp to ensure inbound SSH is reachable — granting the operator persistent remote access to the installer's host. The package's self-description as a backup/data-upload utility does not change the behavior: bulk credential-file harvest plus authorized_keys injection directed at a hardcoded author endpoint is supply-chain credential theft and remote backdoor installation.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for ts-ankle (version 1.1.0).
If you installed it — respond
ts-ankle 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 ts-ankle 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
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks ts-ankle-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.