← Radar

Incident case file

Sign in to watch

Lottie Player — Supply Chain Attack via Compromised npm Package

Incident date Oct 30, 2026Last updated Nov 10, 2026

1 views

ResolvedEthereumMulti-chainSupply chain attack / npm compromiseCluster: LOTTIE-SUPPLY-2026-10

Estimated loss

$1M

Affected users

Number of affected users is not confirmed
Group joining is coming soon.

Investigation

85%

Facts and investigation

Ledger

Attacker

Unknown threat actor (compromised LottieFiles npm maintainer account)

Funds moved to

TODO — specific attacker drain addresses not publicly confirmed

Linked

Attack executed via a malicious version of the @lottiefiles/lottie-player npm package (versions 2.0.5, 2.0.6, 2.0.7) published on October 30–31, 2026. The package injected a wallet-draining script into front-ends of dApps using the library. Multiple DeFi protocols and Web3 front-ends were affected. The package was pulled and clean versions restored within hours of detection.

Chronology

1 beat
  1. On October 30–31, 2026, attackers who had compromised a LottieFiles npm maintainer account published malicious versions of the @lottiefiles/lottie-player package (v2.0.5–2.0.7) containing wallet-draining code. Any dApp front-end that auto-updated to these versions began injecting malicious scripts into user sessions, prompting wallet connection requests and draining assets. Approximately $1M in user funds was stolen before the attack was identified by security researchers. LottieFiles revoked the compromised account, pulled the malicious versions, and published a clean release. Affected dApps were advised to pin to a safe version. The malicious versions remained active for approximately 24 hours.

Sources and coverage

Victim testimonies

No testimonies yet.

+ Add my testimony → (coming soon)