npm: 34 Malicious Packages Disclosed in 7-Minute Window
On July 19-20, 2026, 34 malicious npm packages were disclosed within a tight 7-minute window, exhibiting multiple distinct naming patterns suggestive of various supply chain attack vectors.
Key findings
- 34 malicious npm packages were disclosed within a 7-minute window.
- The packages impersonated various brands, including Twilio, Tencent, and others.
- Multiple packages used scoped names (e.g.,
@akrai/core,@iphouse/api) alongside unscoped versions, indicating a broad impersonation strategy. - All advisories were published on July 19-20, 2026, between 23:53 UTC and 00:00 UTC.
On July 19-20, 2026, a significant burst of 34 malicious packages was disclosed on the npm registry, all within an exceptionally tight 7-minute window. This rapid succession of advisories, published between 23:53 UTC on July 19 and 00:00 UTC on July 20, strongly indicates a coordinated takedown effort by security researchers. The sheer volume and speed of this disclosure underscore the ongoing vigilance required in maintaining software supply chain integrity, as these packages were swiftly identified and removed from public access. While specific details regarding the threat actor or the full extent of their campaign remain undisclosed, the coordinated nature of the takedown points to a proactive response to a multi-faceted attack.
The disclosed packages exhibited a diverse array of naming patterns, suggesting a broad and varied targeting strategy rather than a single, unified typosquatting theme. One prominent group of packages directly impersonated Twilio-related utilities, including names such as twilio-platform-async-data-fetch, twilio-platform-request, org-twilio-phone-numbers-utils, twilio-assets, twilio-deploy, twilio-internal, twilio-serverless, and twiliointernal-messaging-toolbox. Another set of packages appeared to target the "Aftermath" ecosystem, with names like aftermath-finance, aftermath-sui, and aftermathfi. Further impersonation attempts were observed targeting Tencent, with packages named zer0onetencent and zer0onetencent2. A substantial portion of the burst involved packages mimicking "Akrai," "Iphouse," and "Markscan" brands, appearing both as scoped packages (e.g., @akrai/core, @iphouse/api, @markscan/api) and their unscoped counterparts (e.g., akrai-report, iphouse, markscan). This dual approach of using both scoped and unscoped names for the same brand suggests an attempt to maximize reach and exploit different dependency resolution mechanisms. The remaining packages, such as chart-animation-helper and zoom-widget-xss-poc-paresh, appeared to be more ad-hoc or potentially part of smaller, unrelated campaigns caught in the same disclosure window.
While the specific behavioral findings for each of these 34 malicious npm packages were not detailed in the public advisories, the rapid disclosure and removal from the registry confirm their classification as harmful. Malicious packages in the npm ecosystem commonly employ tactics such as exfiltrating sensitive environment variables, injecting malicious code into build processes, establishing remote command-and-control (C2) communication, or deploying cryptocurrency miners. The absence of detailed behavioral reports in this instance means we cannot pinpoint the exact methods used by these particular packages. However, the coordinated nature of their disclosure strongly implies that security mechanisms successfully identified and neutralized these threats before widespread impact could occur, based on their observed malicious activities or suspicious characteristics.
The implications of installing any malicious package are severe. Developers who may have inadvertently downloaded or integrated any of these packages into their projects should consider their systems to be fully compromised. The standard recommendation in such scenarios is to treat the affected environment as untrusted. This necessitates a comprehensive security response, including the immediate rotation of all credentials, API keys, and sensitive tokens that were accessible from the compromised machine or build environment. Furthermore, any systems that consumed artifacts built from the compromised environment should also be thoroughly audited and potentially remediated, as the malicious code could have propagated downstream.
To mitigate potential exposure, developers and organizations should immediately audit their project dependencies. Specifically, review package-lock.json, yarn.lock, or pnpm-lock.yaml files for any of the disclosed package names. If any of these packages are found, they should be promptly removed, and a thorough security audit of the affected development environment and deployed applications should be performed. It is also crucial to review npm token logs for any unauthorized publish events or suspicious activity that might indicate a broader compromise of developer accounts. A representative subset of the malicious package names includes: twilio-platform-async-data-fetch aftermath-finance @akrai/core zer0onetencent iphouse-api markscan-utils Proactive measures such as implementing stricter dependency policies, utilizing software composition analysis (SCA) tools, and enabling multi-factor authentication for all registry accounts are essential to prevent future compromises.
This burst of 34 malicious npm packages, disclosed within a mere seven minutes, serves as a stark reminder of the persistent and evolving threats targeting open-source software supply chains. The attackers' strategy of employing diverse naming conventions, including brand impersonation and both scoped and unscoped package names, highlights an adaptive approach to evade detection and maximize potential impact. While the rapid coordinated disclosure demonstrates the effectiveness of current security monitoring and response capabilities within the npm ecosystem, the sheer volume of such incidents underscores the continuous need for vigilance from both platform maintainers and individual developers. This event reflects the ongoing cat-and-mouse game between malicious actors seeking to exploit trust in the open-source ecosystem and the security community working to protect it.