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

amplitude-ma-tsnpm

Malicious code in amplitude-ma-ts (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3028
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall amplitude-ma-ts

What this malware does

npm stealer. Hardcoded Discord webhook id 1497047226428690432 in postinstall Folder/bin/S.js. Exfils {hostname, whoami, pwd, public_ip (api.ipify.org), /etc/hosts} via Discord embed. v1.0.21 empty placeholder, v1.0.22 shipped payload — name-squat-then-poison. Typosquats @amplitude/* analytics scope. Maintainer 4senna [email protected] (Gmail plus-alias throwaway). Score 20, signals: install_hook + nodejs_phone_home + iplookup_website + discord_bot + discord_exfil + exfil_whoami_hostname. Report: data/reports/research-threat-analysis/reports/2026-04-24-amplitude-ma-ts.md

The package amplitude-ma-ts was found to contain malicious code.

The OpenSSF Package Analysis project identified 'amplitude-ma-ts' @ 1.0.22 (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

1 flagged
1.0.22

Indicators of compromise (SHA-256)

2cba685b107eb30c1b216522bcb10e36df5eb8096a549b86ed097b9dbc7f192c
88366a7453a0226ce379fc1e267e15daf9e3c144387e614528c88ab30cb0a49c

Detection & response playbook

Credential / info stealer

  1. Find it

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

  2. If you installed it — respond

    amplitude-ma-ts 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.

  3. Did it already run?

    If amplitude-ma-ts 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 amplitude-ma-ts 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. amplitude-ma-ts on npm has been identified as a malicious package (version 1.0.22 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder
  • SafeDep · finder

Detect & block this

O3 blocks amplitude-ma-ts-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring
amplitude-ma-ts (npm) malicious package — MAL-2026-3028 | O3 Security