Briefing
Amazon Inspector identified a massive, coordinated supply chain attack targeting the npm registry and the open-source reward mechanism of the tea.xyz protocol. The primary consequence is the systemic pollution of the open-source ecosystem, which fundamentally undermines the integrity of software dependencies used across Web3 and traditional finance. This unprecedented event involved the automated publishing of over 150,000 malicious packages designed to illegitimately claim cryptocurrency rewards. The campaign’s scale represents a new, financially-motivated threat model for open-source infrastructure.
Context
The open-source software supply chain has long been a critical, unmanaged attack surface where trust in third-party dependencies is often implicit. This pre-existing risk is now critically amplified by token incentive programs that link code contribution directly to financial reward. This financialization creates a direct, scalable economic motive for sophisticated supply chain fraud, shifting the threat from mere vandalism to industrial-scale asset acquisition.
Analysis
The attacker leveraged self-replicating automation to generate and publish non-functional packages to the npm registry at an industrial scale. The core vector was the systematic inclusion of a tea.yaml file within each package, which covertly linked the malicious code to an attacker-controlled blockchain wallet address. This process successfully weaponized the protocol’s reward system, exploiting the logic that grants token farming rewards based on the presence and apparent contribution of a package in the registry. The automation allowed the threat actor to bypass traditional detection methods and achieve an exponential rate of registry pollution.
Parameters
- Total Malicious Packages → 150,000+ packages published. (Largest package flooding incident in open-source registry history).
- Attack Vector → Supply Chain Pollution. (Systematic publication of malicious packages to the npm registry).
- Targeted Mechanism → Open-Source Reward System. (The protocol’s token farming and contribution-linking logic).
Outlook
Protocols relying on open-source contributions must immediately implement rigorous, automated dependency scanning and contribution validation that goes beyond simple existence checks. The second-order effect is a necessary and immediate shift in security best practices toward a “zero-trust” model for all third-party code. New standards for package provenance and proof-of-contribution are now required to mitigate future incentive-driven supply chain attacks and protect the integrity of the core Web3 development stack.
Verdict
This attack establishes a new, scalable blueprint for economic fraud against open-source incentive layers, proving that financialization has permanently weaponized the software supply chain.
