npm: Coordinated Takedown Removes 20 Malicious Packages, Many with Themed Naming, in Under a Minute

Key findings

• 20 malicious npm packages were disclosed in under one minute on November 4, 2026.
• Many packages followed a distinct 'adjective_animal_color-number' naming convention.
• All disclosed packages were rated Critical severity, indicating severe compromise potential.
• The burst included a mix of older, low-download packages and a more recent scoped package.
• No specific behavioral findings or C2 domains were detailed in the advisories.

On November 4, 2026, a coordinated disclosure event on npm led to the removal of twenty malicious packages within an extremely tight window of under one minute. This rapid takedown highlights an active monitoring and response effort against a diverse set of malicious artifacts, ranging from older, low-download packages to a more recently published scoped package.

The majority of the packages, fifteen out of twenty, followed a peculiar "adjective_animal_color-number" naming convention. Examples include southern_duck_tan-16, xenacious_kangaroo_blush-47, pure_opossum_amaranth-54, smooth_angelfish_emerald-54, and sound_deer_apricot-15. These packages were all first published around May 21, 2024, approximately 2.5 years prior to their disclosure, and maintained very low download counts, typically around 60 per week. This suggests they were either dormant malicious packages awaiting activation or older, low-profile legitimate packages that were compromised. Alongside these, other notable packages included gugodapis (first published May 9, 2024), babyyodaa (first published September 27, 2021), and the exceptionally old et_phone_home (first published April 15, 2015, over 11 years ago). The burst also included the scoped package @signals-notebook/annotation-editor, first published more recently on April 9, 2026, approximately seven months before its removal. Across the board, all these packages exhibited very low download numbers, indicating a limited install base for the malicious versions, but their longevity or specific naming patterns suggest a deliberate, if varied, campaign.

Specific behavioral findings for these malicious packages were not detailed in the provided advisories. However, the consistent "Critical" severity assigned to all twenty packages indicates a severe potential impact on any system that installed them. Typically, a critical severity rating in such cases implies that the package could allow for arbitrary code execution, data exfiltration, or full system compromise.

For any system that installed one of these malicious packages, the standard recommendation is to consider the affected system fully compromised. This necessitates a thorough security audit and immediate action to mitigate potential damage. Users should rotate all credentials and secrets from a separate, trusted machine, as compromised systems cannot be relied upon for secure operations.

Developers are strongly advised to audit their package-lock.json or yarn.lock files for the presence of any of the disclosed package names. If found, these dependencies should be immediately removed and all associated credentials rotated. Organizations should also review their npm token logs for any unauthorized publishes or suspicious activity around the time of the packages' first publication or recent updates. A representative list of package names to check for includes:

• southern_duck_tan-16
• xenacious_kangaroo_blush-47
• et_phone_home
• babyyodaa
• @signals-notebook/annotation-editor

This coordinated takedown of a diverse set of malicious npm packages in such a tight timeframe underscores the continuous efforts by security teams to protect the open-source ecosystem. The mix of older, low-download packages alongside a newer scoped package suggests that attackers are employing varied strategies, from reactivating dormant malicious code to targeting specific package types, all while security researchers are rapidly identifying and responding to these threats.