dynstrg-howtonpm
Advisory published Updated
dynstrg-howto is a confirmed malicious npm package (MAL-2026-12787) that executes malicious code on install (malicious versions 1.0.1, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dynstrg-howto (npm)
What this malware does
package.json declares a preinstall hook that runs index.js on npm install. index.js collects the installer's hostname, username, home directory, DNS server list, and reads /etc/passwd and /etc/hosts, then HTTPS-POSTs the collected JSON to the hardcoded out-of-band endpoint idzskk7dl8mrfoqx6thyhegqbhha50tp.oastify.com (Burp Collaborator subdomain). Execution is automatic on default install; the destination is attacker-controlled and unrelated to any declared package purpose.
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
Malicious packageFind it
Search your lockfiles and build artifacts for dynstrg-howto (2 malicious versions).
If you installed it — respond
Remove dynstrg-howto from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If dynstrg-howto 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
- ReversingLabs · finder
Detect & block this
O3 blocks dynstrg-howto-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.