Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

dynstrg-howtonpm

dynstrg-howto is a confirmed malicious npm package (MAL-2026-12787) that executes malicious code on install (malicious version 1.0.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.

Malicious versions

1 flagged
1.0.1

Indicators of compromise (SHA-256)

800fab99d95f1a2cef6ebf269ca240bf60518735cfb58c7c24b6a8474c72ee77

Detection & response playbook

Malicious package
  1. Find it

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

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

  4. How O3 protects you

    O3 blocks dynstrg-howto 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. dynstrg-howto on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014944

References

Credits

  • Amazon Inspector · 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