What does the amplitude-ma-ts malware do?

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 (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. Any computer that has this package installed

Which versions of amplitude-ma-ts are malicious?

The following npm versions of amplitude-ma-ts are flagged malicious: 1.0.21, 1.0.22, 1.0.23, 1.0.24. Treat any of these as compromised.

How do I remediate amplitude-ma-ts if I installed it?

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.

I already installed amplitude-ma-ts — how do I know if it already compromised me?

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.

Is amplitude-ma-ts part of a known attack campaign?

Yes — amplitude-ma-ts is associated with the GHSA-987f-7782-4mjj campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find amplitude-ma-ts across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for amplitude-ma-ts (4 malicious versions). 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.

Malicious package

amplitude-ma-tsnpm

amplitude-ma-ts is a confirmed malicious npm package (MAL-2026-3028) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.21, 1.0.22, 1.0.23…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in amplitude-ma-ts (npm)

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.

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.

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

4 flagged

1.0.211.0.221.0.231.0.24

Indicators of compromise (SHA-256)

2cba685b107eb30c1b216522bcb10e36df5eb8096a549b86ed097b9dbc7f192c

88366a7453a0226ce379fc1e267e15daf9e3c144387e614528c88ab30cb0a49c

b1c8391060a42708e68425943e4a2f779e2ce09e51ca578282148df1e761affd

Detection & response playbook

Credential / info stealer

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 (4 malicious versions). 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.
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.
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.
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 (versions 1.0.21, 1.0.22, 1.0.23, 1.0.24 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-987f-7782-4mjj

References

github.com

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

Explore

All malware advisories How O3 detects malware Vulnerability database