npm: 4 Malicious '@medisend' Scoped Packages Among 19 Disclosed in Under a Minute

Key findings

• 19 malicious npm packages were disclosed within a single minute on August 24, 2026.
• Four of the disclosed packages shared the @medisend npm scope, indicating a targeted campaign.
• All nineteen packages were assigned a Critical severity rating, signaling high potential for compromise.
• Several packages were published just hours or days before disclosure, suggesting fresh malicious uploads.

On August 24, 2026, nineteen malicious npm packages were disclosed within a single minute, signaling a highly coordinated supply chain attack. This rapid disclosure event, anchored by advisories like GHSA-4v36-qjgj-x7xf, highlights the swift action taken to remove these threats from the npm registry. Notably, several of these packages, such as dim-hydration-ui (published just 18 hours prior) and the four packages under the @medisend scope (published 19-20 hours prior), were very recently introduced, suggesting a fresh wave of malicious uploads rather than compromises of long-standing projects.

The coordination of this burst is evident through the tight disclosure window and, more specifically, the shared @medisend scope among four of the packages: @medisend/auth, @medisend/core, @medisend/shared, and @medisend/webview-bridge. This shared naming convention strongly suggests a targeted campaign. The remaining fifteen packages, including secret-key-totp, paypal-business-sdk, web-advertising, openai-pr-reviewer, and kelly-stake-sizing, do not exhibit an obvious common naming pattern, though their simultaneous disclosure points to a single, broader malicious operation. These could represent ad-hoc typosquats or attempts to mimic legitimate package names without a consistent scheme.

While specific behavioral findings for each package were not detailed in the advisories, the "Critical" severity assigned to all nineteen packages indicates a high potential for severe compromise. Malicious packages in the npm ecosystem frequently employ tactics such as exfiltrating sensitive environment variables, stealing credentials, installing backdoors, or establishing remote command-and-control channels. The extracted IOCs, including domains like 7iqn7pls4ly6w8valba0xcxygpmha7yw.oastify.com and da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun, are commonly associated with data exfiltration or callback mechanisms, suggesting that these packages likely attempted to communicate with external infrastructure to deliver their malicious payloads or siphon off stolen information.

The "Critical" severity rating means that any system that installed these malicious packages should be considered fully compromised. Developers and organizations are strongly advised to treat such incidents with the utmost gravity. The potential impact ranges from unauthorized access to sensitive data and intellectual property to the complete takeover of development environments, leading to further supply chain attacks.

Given the nature of this coordinated attack, developers should immediately audit their package-lock.json or yarn.lock files for any of the disclosed package names. If any are found, the affected systems should be isolated, and all credentials (API keys, tokens, passwords) that were accessible from those environments must be rotated from a separate, secure machine. Furthermore, organizations should review their npm token logs for any unauthorized publish events that might indicate a compromised maintainer account. A representative list of the malicious packages includes: @medisend/auth @medisend/core @medisend/shared @medisend/webview-bridge secret-key-totp paypal-business-sdk web-advertising openai-pr-reviewer

This burst underscores the persistent and evolving threat landscape within open-source software supply chains. The rapid deployment and subsequent coordinated disclosure of these packages demonstrate both the attackers' agility and the security community's increasing effectiveness in identifying and mitigating such threats. The combination of scoped packages and seemingly disparate names within a single, tight window suggests a sophisticated adversary employing varied tactics to maximize their reach and evade detection.