amplitude-session-replaynpm
amplitude-session-replay is a confirmed malicious npm package (MAL-2026-15497) that executes malicious code on install (malicious version 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in amplitude-session-replay (npm)
What this malware does
package.json declares a dependency whose key is the package's own name (amplitude-session-replay) and whose value is a plain HTTPS URL, https://repo.securityctrl.com/amplitude-session-replay, instead of a registry version range. On npm install, npm fetches the tarball bytes returned by that URL and installs whatever it contains, including running any lifecycle scripts inside — with no version pin, no integrity hash, and no registry vetting. The shipped source in the published tarball is an inert stub, so the manifest itself is the delivery mechanism: whoever controls repo.securityctrl.com controls code executed on the installer's machine at install time. The self-referential dependency name (dependency-confusion shape) also encourages resolvers to prefer this entry over any legitimately-named amplitude-session-replay package. The host is unrelated to Amplitude's own domains.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for amplitude-session-replay (version 45.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging amplitude-session-replay across your stack and pipelines.
If you installed it — respond
Remove amplitude-session-replay 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 amplitude-session-replay 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-session-replay 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks amplitude-session-replay-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.