NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

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)

MAL-2026-12787
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall dynstrg-howto

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

2 flagged
1.0.11.1.1

Indicators of compromise (SHA-256)

800fab99d95f1a2cef6ebf269ca240bf60518735cfb58c7c24b6a8474c72ee77
687ddbe581731d5da84cb2a0e04508c31995cbc7fdd378b53090ac8b9a51a0d2
545d5d0e2e8e5ec332762e5afca7db5ad6f8762b0fc5ef5b0739818452497ce3
85640741bbd26fb1ab318a147acfe8233f492fa11a5c090e5999c84e7b984d4d

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for dynstrg-howto (2 malicious versions).

  2. 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.

  3. 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

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

Campaign

IN-MAL-2026-014944GHSA-p2vx-mw75-76fwIN-MAL-2026-019775RLMA-2026-10715

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.

Explore

dynstrg-howto (npm) malicious package — MAL-2026-12787 | O3 Security