# Lottie Player Supply Chain Attack: Supply chain attack on Lottie Player animation library drained crypto wallets on 178+ websites
Source page: https://vaultx.llc/hacks/crypto-stealing-malware-on-178-websites · VaultX incident report by Sentinel · first published 2026-11-17, updated 2026-11-17
- Date: 2024-10-30
- Reported loss: $723K (reported $723,000+ tracked across multiple victims; full extent uncertain due to unreported incidents)
- Attribution: unknown; attackers compromised the Lottie Player library distribution
- Chains: Ethereum, BNB Chain, Polygon, Arbitrum
- Status: resolved
- Severity: 62/100
- Response score: 75/100 (Fast containment within 24 hours; clean versions released quickly; affected sites notified; transparent disclosure)
On October 30-31, 2024, attackers compromised three versions (2.0.5, 2.0.6, 2.0.7) of the widely-used Lottie Player animation library, injecting wallet-draining malware that affected over 178 websites. The malicious code targeted users connecting cryptocurrency wallets to affected sites, prompting fake transaction approvals that redirected funds to attacker-controlled addresses. According to security researchers, at least $723,000 was stolen across multiple victims during the approximately 24-hour compromise window. LottieFiles quickly released clean versions and the compromised code was removed from CDN distribution.

**What happened**
In late October 2024, attackers executed a supply chain attack by compromising the Lottie Player library, a popular open-source animation tool used by hundreds of websites. According to BleepingComputer and Cloudflare's security blog, three specific versions of the library (2.0.5, 2.0.6, and 2.0.7) were injected with crypto-draining malware between October 30-31, 2024.
The compromised library affected over 178 websites, including major cryptocurrency platforms such as 1inch (a decentralized exchange aggregator), TEN Finance, and Vultisig, along with various other DeFi protocols. When users visited these affected websites and connected their cryptocurrency wallets, the malicious code would activate.
According to reports from security firm Blockaid and tracked by blockchain analysts, the malware detected wallet connections and prompted fake transaction approval requests. When users approved what appeared to be legitimate transactions, funds were instead redirected to attacker-controlled addresses. One victim reportedly lost $10,000 in a single transaction, and security researchers tracked at least $723,000 stolen across multiple victims.
The attack lasted approximately 24 hours before being detected and publicly disclosed on October 31, 2024. LottieFiles, the company behind Lottie Player, quickly responded by releasing clean versions of the library and removing the compromised versions from CDN distribution. The relatively short duration of the compromise and rapid response likely limited the total damage, though the full extent of losses remains uncertain as many victims may not have reported thefts.

**How it worked**
The attack exploited the trust model of software supply chains by compromising a widely-used third-party library. Lottie Player is a JavaScript library that renders animations on websites, making it a common dependency for modern web applications. By injecting malicious code into versions 2.0.5, 2.0.6, and 2.0.7, the attackers ensured their payload would be automatically distributed to all websites using these versions through CDN services.
According to Cloudflare's technical analysis, the injected malware specifically targeted cryptocurrency wallet interactions. When a user on an affected website initiated a wallet connection (using tools like MetaMask, WalletConnect, or similar), the malicious code would intercept the connection process. It then generated fraudulent transaction requests that appeared legitimate to the user but actually contained instructions to transfer funds to attacker-controlled addresses.
The malware was designed to target multiple blockchain networks including Ethereum, Binance Smart Chain, Polygon, and Arbitrum, along with various token standards (ERC-20, BEP-20). This multi-chain approach maximized the attack surface. The fake transaction prompts were crafted to appear as normal approval requests, exploiting users' familiarity with routine wallet interactions on DeFi platforms. Once users approved these transactions, their ETH, stablecoins, and other tokens were immediately transferred to the attackers' wallets.

**Where the money went**
According to reports, stolen funds totaling at least $723,000 were transferred to attacker-controlled addresses across Ethereum, BNB Chain, Polygon, and Arbitrum. Security researchers tracked multiple theft transactions, including one incident where a victim lost $10,000. No information is available in the research about the use of mixers, bridges, or exchanges for laundering. No funds were reported as frozen or recovered.

**The response**
LottieFiles responded quickly to the compromise, releasing clean versions of the Lottie Player library and removing the malicious versions (2.0.5, 2.0.6, 2.0.7) from CDN distribution within approximately 24 hours of the attack beginning. According to Cloudflare's blog, affected websites were notified to update their dependencies immediately. Security researchers published indicators of compromise to help identify affected sites. The company's rapid response likely limited the total damage by containing the attack to a roughly 24-hour window.

**Impact**
The attack affected over 178 websites including major DeFi platforms such as 1inch, TEN Finance, and Vultisig. According to tracked transactions, at least $723,000 was stolen from multiple victims, though the full extent remains uncertain due to potentially unreported incidents. The 24-hour compromise window and quick response likely prevented significantly larger losses. The incident highlighted the ongoing vulnerability of cryptocurrency users to supply chain attacks and the risks of third-party dependencies in web3 applications. No specific market price impacts on affected platforms' tokens were reported in the research.

**Timeline**
- 2024-10-30 Malicious code injected into Lottie Player versions 2.0.5, 2.0.6, and 2.0.7; crypto-draining attacks begin on 178+ affected websites
- 2024-10-31 Security researchers publicly disclose the supply chain attack; LottieFiles releases clean versions and removes compromised code from CDN
- 2024-10-31 Affected websites notified to update dependencies; attack contained after approximately 24-hour window

**How to protect yourself**
- Supply chain attacks remain a critical threat vector in crypto: even trusted, widely-used libraries can be compromised to inject wallet-draining malware affecting hundreds of websites simultaneously.
- Users should carefully review all transaction approval requests, even on familiar platforms, and verify recipient addresses before approving any wallet transactions, as malware can generate convincing fake prompts.
- Projects should implement subresource integrity (SRI) checks for third-party libraries, use dependency pinning rather than auto-updating to latest versions, and monitor for unexpected changes in library behavior.
- The 24-hour attack window demonstrates the importance of rapid incident detection and response systems; security monitoring tools and anomaly detection can significantly limit damage from supply chain compromises.
- Consider using hardware wallets with transaction verification screens that display full recipient addresses, making it harder for malware to trick users into approving fraudulent transactions.

**Still unknown**
- The exact total amount stolen remains uncertain; the $723,000 figure represents tracked transactions but actual losses could be higher due to unreported incidents
- The identity and attribution of the attackers who compromised the Lottie Player library is unknown
- How the attackers gained access to inject malicious code into the Lottie Player distribution system is not detailed in available reports
- Specific wallet addresses controlled by the attackers are not published in the research
- Whether any stolen funds have been frozen, recovered, or tracked through mixers and exchanges is not reported
- The exact number of individual victims affected and the distribution of losses across different platforms is unclear

**Sources**
- Lottie Player supply chain attack impacts over 178 websites https://www.bleepingcomputer.com/news/security/lottie-player-supply-chain-attack-impacts-over-178-websites/
- Cloudflare Blog: Lottie Player supply chain attack https://blog.cloudflare.com/lottie-player-supply-chain-attack
- Lottie Player supply chain attack embeds crypto drainer https://cointelegraph.com/news/lottie-player-supply-chain-attack-crypto-drainer

---
VaultX: free crypto news and intelligence, https://vaultx.llc
