sm-checkout

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (0bc8dabb0ecf46dc57dd07dacdf28c9cddf629ffb8e9b0cea75e71cd999feaf0)
[email protected] declares preinstall and postinstall lifecycle scripts in package.json that invoke curl against a hardcoded bare-IP URL over plain HTTP (http://16.192.173.5/sm-checkout/pre and http://16.192.173.5/sm-checkout/post) on npm install. The inflated 99.0.0 version is calibrated to win semver resolution against a private package of the same name, and the lifecycle callbacks confirm successful execution on any host that mistakenly resolves the public name, leaking the installer's source IP and install timing to the operator of 16.192.173.5. A source comment self-labels the package as a dependency-confusion test; the labelling does not change that the artifact runs an unauthenticated outbound beacon on every install in build systems and developer machines that pull it.

## Source: ghsa-malware (897b995712d1f63fb75db33a78c7e8fff81d49fd3a5fb05dca13613e6d80d1e9)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

## Source: ossf-package-analysis (7e0e304166bd31c7677998bce3b0fa29ce87fcf40861c714a8f69417fc1083d1)
The OpenSSF Package Analysis project identified 'sm-checkout' @ 99.0.1 (npm) as malicious.

It is considered malicious because:

- The package executes one or more commands associated with malicious behavior.

Compromised versions (2)

• 99.0.0
• 99.0.1

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.