Malicious code in amplitude-session-replay (npm)
Published Sources: OSV (Schadpakete)
- Malicious package
What is affected, what to do
Uninstall the package, isolate affected environments and rotate credentials that were available during installation.
Not sure whether and how you are affected? Ask a question about this vulnerability
Malicious package
npmamplitude-session-replay
“amplitude-session-replay” is registered as malicious in the npm repository. Anyone who installed the package should uninstall it immediately, isolate affected environments and rotate credentials that were present during installation.
Affected versions (1)
- 45.0.0
purl: pkg:npm/amplitude-session-replay
Sources (2)
amazon-inspector
IN-MAL-2026-019075Versions from this source: 45.0.0
sha256: fb71ca2dc9e74e42a64b1533ecb98ea1cad26e283b0c3d3ba0f4e7c760fac713
ghsa-malware
GHSA-jvwx-f8cc-jjj8sha256: 45e75fc14fb647bfdf2d3b2a2bffa4d843f51e4a4970cadcde65c1daca37d7c1
The OSSF `malicious-packages` namespace lists packages flagged as malicious by static analysis or sandbox detonation. An entry here is a confirmed finding, not a suspicion.
Metrics
—
Priority
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 24.77 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (fb71ca2dc9e74e42a64b1533ecb98ea1cad26e283b0c3d3ba0f4e7c760fac713)
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.
Source: ghsa-malware (45e75fc14fb647bfdf2d3b2a2bffa4d843f51e4a4970cadcde65c1daca37d7c1)
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.