Malicious code in sm-checkout (npm)
The npm package 'sm-checkout' versions 99.0.0 and 99.0.1 contain malicious lifecycle scripts that execute during installation. These scripts perform unauthenticated outbound HTTP requests to a hardcoded IP address, leaking the installer's source IP and timing information. The package uses an inflated version number to supersede legitimate packages with the same name, facilitating dependency confusion attacks. This behavior is confirmed by multiple sources identifying the package as malicious.
AI Analysis
Technical Summary
The 'sm-checkout' npm package at versions 99.0.0 and 99.0.1 includes preinstall and postinstall scripts that invoke curl commands to a hardcoded bare-IP URL over plain HTTP (http://16.192.173.5/sm-checkout/pre and /post). This results in an unauthenticated outbound beacon on every install, leaking the source IP and install timing to the operator of the IP address. The package's versioning is deliberately inflated to win semver resolution against private packages of the same name, enabling it to be installed inadvertently in build systems and developer environments. The package is self-labeled as a dependency-confusion test but still performs malicious network activity. The OpenSSF Package Analysis project has flagged version 99.0.1 as malicious due to execution of commands associated with malicious behavior.
Potential Impact
Installation of the affected 'sm-checkout' package versions causes the host to make unauthenticated outbound HTTP requests to a malicious server, leaking sensitive metadata such as source IP and install timing. This can compromise privacy and potentially aid attackers in reconnaissance or further attacks. The package's inflated version number increases the risk of accidental installation via dependency confusion. No direct code execution or payload delivery beyond the beaconing is described.
Mitigation Recommendations
Avoid installing the 'sm-checkout' package versions 99.0.0 and 99.0.1. Remove these versions from any build or deployment pipelines. Use package integrity verification and strict dependency resolution to prevent dependency confusion attacks. Monitor package sources carefully and prefer official or trusted packages. Patch status is not yet confirmed — check the vendor advisory or npm security advisories for updates or removals of the malicious package.
Malicious code in sm-checkout (npm)
Description
The npm package 'sm-checkout' versions 99.0.0 and 99.0.1 contain malicious lifecycle scripts that execute during installation. These scripts perform unauthenticated outbound HTTP requests to a hardcoded IP address, leaking the installer's source IP and timing information. The package uses an inflated version number to supersede legitimate packages with the same name, facilitating dependency confusion attacks. This behavior is confirmed by multiple sources identifying the package as malicious.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The 'sm-checkout' npm package at versions 99.0.0 and 99.0.1 includes preinstall and postinstall scripts that invoke curl commands to a hardcoded bare-IP URL over plain HTTP (http://16.192.173.5/sm-checkout/pre and /post). This results in an unauthenticated outbound beacon on every install, leaking the source IP and install timing to the operator of the IP address. The package's versioning is deliberately inflated to win semver resolution against private packages of the same name, enabling it to be installed inadvertently in build systems and developer environments. The package is self-labeled as a dependency-confusion test but still performs malicious network activity. The OpenSSF Package Analysis project has flagged version 99.0.1 as malicious due to execution of commands associated with malicious behavior.
Potential Impact
Installation of the affected 'sm-checkout' package versions causes the host to make unauthenticated outbound HTTP requests to a malicious server, leaking sensitive metadata such as source IP and install timing. This can compromise privacy and potentially aid attackers in reconnaissance or further attacks. The package's inflated version number increases the risk of accidental installation via dependency confusion. No direct code execution or payload delivery beyond the beaconing is described.
Mitigation Recommendations
Avoid installing the 'sm-checkout' package versions 99.0.0 and 99.0.1. Remove these versions from any build or deployment pipelines. Use package integrity verification and strict dependency resolution to prevent dependency confusion attacks. Monitor package sources carefully and prefer official or trusted packages. Patch status is not yet confirmed — check the vendor advisory or npm security advisories for updates or removals of the malicious package.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-14397
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a8c4c6facd9273b499c0cbc
Added to database: 08/24/2026, 13:51:43 UTC
Last enriched: 08/24/2026, 14:26:11 UTC
Last updated: 08/24/2026, 16:03:14 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.