Skip to main content
Mallory
← Back to News
package-repository-poisoningdependency-confusion-typosquatbuild-pipeline-compromise

Automated Supply Chain Campaign Flooded npm With 800 Malicious Packages

Supply Chain Risk · 3 sources · Updated 3mo ago · First seen Feb 23, 2022

Automated Supply Chain Campaign Flooded npm With 800 Malicious Packages

Researchers linked a threat actor tracked as RED-LILI to a large-scale software supply chain attack that pushed nearly 800 malicious packages to the npm registry in a burst of activity over roughly a week. Checkmarx reported the operation began around February 23, 2022, and relied on a highly automated pipeline that created a separate npm account for each package, complicating bulk detection and takedown efforts. The campaign used custom Python tooling, Selenium, and the open-source Interactsh project to automate account creation and bypass npm email one-time-password verification during signup.

The malicious packages were part of a broader effort to compromise developers and downstream environments through common package ecosystem abuse techniques, including typosquatting and dependency confusion. Reporting tied the activity to packages crafted to target organizations such as Azure, Uber, and Airbnb, underscoring how attackers can industrialize package publication at scale and turn open-source repositories into an efficient delivery channel for supply chain compromise.

Does this reach your builds?Trace attribution and downstream blast radius.
Trace the chain
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

3 events · Feb 23, 2022
  1. Reported Mar 29, 20225y ago

    Checkmarx discloses RED-LILI-linked NPM supply chain campaign

    Checkmarx publicly analyzed the large-scale campaign and described the attacker’s automated workflow using custom Python, Selenium, and Interactsh to bypass NPM signup OTP verification and publish malicious packages. The report linked the activity to dependency confusion and typosquatting targeting developers associated with Azure, Uber, and Airbnb.

    A Large-Scale Supply Chain Attack Distributed Over 800 Malicious NPM Packages
  2. Reported Mar 29, 20225y ago

    Nearly 800 malicious NPM packages published over about a week

    After the initial activity was observed, the attacker published nearly 800 malicious NPM packages in bursts over roughly a week. The packages were distributed across one account per package to hinder bulk detection and takedown.

    A Large-Scale Supply Chain Attack Distributed Over 800 Malicious NPM Packages
  3. Feb 23, 20225y ago

    Malicious NPM package campaign first observed

    Checkmarx said the earliest evidence of anomalous activity tied to the RED-LILI-linked NPM supply chain campaign was observed on February 23, 2022. The operation involved automated creation of separate NPM accounts for malicious package publication.

    A Large-Scale Supply Chain Attack Distributed Over 800 Malicious NPM Packages
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Threat actors

1 linked

Affected products

1 linked
Npm
Do you run this?See attribution and downstream blast radius, and whether this package or vendor reaches your builds.
Trace the Supply Chain
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.