npm: 11 Malicious Packages, 8 with 'sm-' Prefix, Disclosed in Under a Minute
Key findings • 11 malicious npm packages disclosed simultaneously on August 24, 2026. • 8 packages share the sm- prefix, indicating a coordinated campaign. • All sm- prefixed packages wer…
Key findings
- 11 malicious npm packages disclosed simultaneously on August 24, 2026.
- 8 packages share the
sm-prefix, indicating a coordinated campaign. - All
sm-prefixed packages were first published just 17 hours before disclosure. - OpenSSF Package Analysis detected malicious command execution in
sm-prefixed packages. - All disclosed packages were rated with Critical severity.
On August 24, 2026, eleven malicious packages were simultaneously disclosed on the npm registry, all within a single minute. Eight of these packages, including sm-oauth, sm-cart, and sm-admin, shared a common 'sm-' prefix and were first published just 17 hours before their disclosure, suggesting a rapid deployment of malicious code.
The coordinated nature of this burst is evident in the naming convention of eight of the disclosed packages, all beginning with sm-. This pattern, seen in packages such as sm-oauth, sm-cart, sm-checkout, sm-payment, sm-billing-form, sm-session, sm-apikey-model, and sm-admin, suggests a targeted campaign rather than isolated incidents. The remaining packages, amundi-compare, message-compiler, and fund-calculator, do not share this prefix but were disclosed at the exact same time, indicating they might be part of the same broader operation or opportunistic additions.
OpenSSF Package Analysis identified that the sm- prefixed packages, including sm-cart, sm-checkout, sm-payment, sm-billing-form, sm-session, sm-apikey-model, and sm-admin, all exhibited behavior associated with malicious command execution. This typically involves the package running arbitrary code on the system where it is installed, potentially leading to system compromise or data exfiltration.
The severity of these disclosures is uniformly rated as Critical. This means that any system that installed one of these malicious packages should be considered fully compromised. Users are strongly advised to treat affected systems as untrusted, immediately rotate all credentials and secrets from a separate, secure machine, and conduct a thorough forensic analysis.
Developers should immediately audit their package-lock.json and yarn.lock files for the presence of any of the disclosed malicious packages. If found, these packages must be removed, and all credentials used on the affected development or deployment environments should be rotated. Specific packages to look for include:
sm-oauthsm-cartsm-checkoutsm-paymentsm-billing-formsm-sessionsm-apikey-modelsm-adminamundi-comparemessage-compilerfund-calculator
Additionally, review npm token logs for any unauthorized publish activity.
This rapid, simultaneous disclosure of multiple malicious packages, particularly those sharing a common naming convention and deployment timeline, highlights the ongoing threat of supply chain attacks targeting package registries. While the specific intent behind this particular campaign is not fully detailed, the consistent 'Critical' severity and command execution behavior across multiple packages underscore the need for vigilance in dependency management and proactive security measures.