npm: 40 Malicious Packages with 'fantastic_z3n' and 'far-' Signatures Disclosed in 4 Minutes

Key findings

• 40 malicious npm packages were disclosed in a coordinated attack.
• All advisories were published within a tight four-minute window on September 10, 2026.
• Packages exhibited common naming patterns, including _z3n, far-, and 0xrequest suffixes/prefixes.
• Every disclosed package was assigned a Critical severity rating, indicating severe system compromise.

On September 10, 2026, a rapid and coordinated supply chain attack targeted the npm ecosystem, with 40 malicious packages disclosed within a tight four-minute window between 10:44 UTC and 10:47 UTC. These packages, many sharing distinct naming conventions such as _z3n, far-, or 0xrequest, were flagged and removed from the registry, highlighting a swift response to a concentrated threat. The coordinated nature of this disclosure suggests a single campaign or actor behind the malicious activity.

The campaign exhibits clear naming patterns, indicating either automated generation or a deliberate thematic approach. A significant number of the malicious packages include the suffix _z3n, such as fantastic_parrotfish_z3n, fantastic_wolf_z3n, and fantastic_bug_z3n. Another prevalent pattern involves the prefix far- (or far_), seen in names like far-jade-porcupine, far-cyan-mite, and far-pink-anglerfish. A smaller subset uses the suffix 0xrequest, exemplified by fantastic_lizard_0xrequest and fantastic_rat_0xrequest. These consistent naming schemes suggest a unified effort rather than disparate, unrelated attacks. While many of these packages had very low download counts (e.g., far-jade-porcupine with 1 download/week, fantastic_peafowl_z3n with 1 download/week), a few, like fantastic_lizard_0xrequest and fantastic_rat_0xrequest, had slightly higher numbers (33 downloads/week each), indicating some level of exposure. The first_published dates for many of these packages are around November 2025, approximately 10 months before their disclosure, suggesting they were dormant or slowly gaining traction before being identified as malicious. However, some packages like fantastic_lizard_0xrequest were first published much earlier, in May 2024, indicating a longer-term presence.

While specific behavioral findings from OpenSSF Package Analysis were not detailed in the advisories, all 40 packages were assigned a Critical severity rating. This universally high severity implies that the malicious code embedded within these packages is capable of severe compromise. Typically, such critical ratings are reserved for threats that can lead to remote code execution, credential exfiltration, or complete system takeover. Without explicit behavioral findings, the exact mechanisms of compromise remain unstated, but the consistent critical assessment underscores the significant danger these packages posed to any system that installed them.

The "Critical" severity assigned to every single one of these 40 packages means that any system that installed an affected version should be considered fully compromised. This is not a minor vulnerability; it suggests that the malicious code could have granted attackers extensive control over the compromised environment. Users are strongly advised to treat such an incident with the utmost seriousness, as it could lead to the exfiltration of sensitive data, installation of further malware, or disruption of operations. The standard recommendation in such cases is to assume a breach and take immediate remediation steps.

Developers and organizations should immediately audit their package-lock.json or yarn.lock files for the presence of any of the disclosed malicious packages. If any are found, the affected systems must be considered compromised. Remediation steps should include rotating all credentials (API keys, tokens, passwords) that were accessible from the compromised environment, ideally from a separate, clean machine. Furthermore, it is crucial to review npm token logs for any unauthorized publish events and to ensure that all development and deployment environments are free of these malicious dependencies. A representative list of affected packages includes:

• far-jade-porcupine
• fantastic_parrotfish_z3n
• fantastic_lizard_0xrequest
• fantastic_rat_0xrequest
• fantastic_goat_dumbs

This burst of 40 malicious npm packages, rapidly disclosed within minutes, serves as a stark reminder of the ongoing and evolving threats within the software supply chain. The use of consistent naming patterns across a large number of packages suggests a deliberate and organized effort by threat actors to inject malicious code into the ecosystem. While the immediate impact in terms of downloads for many of these packages was low, the sheer volume and speed of their disclosure highlight the continuous need for vigilance and robust security practices in dependency management. Such coordinated drops underscore the challenges faced by package registry maintainers and security researchers in identifying and mitigating these threats before they can cause widespread damage.