sm-payment

Details

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

## Source: amazon-inspector (926b17cedd788f5f626b3c4001ca9f1b9572abe425b87d40d6f03814d211e3e7)
package.json declares preinstall and postinstall lifecycle scripts that curl a hardcoded bare IP over plain HTTP (http://16.192.173.5/sm-payment/pre and.../post) automatically on npm install. The package has no build or native-addon purpose that would justify contacting a bare IP at install time; the callbacks fire unsolicited on every install and signal to the operator of that endpoint that the installer's host executed the package. The shape (bare IP, plain HTTP, unrelated to any documented package function, fired from both preinstall and postinstall) is consistent with dependency-confusion / namesquat reconnaissance beacons.

## Source: ghsa-malware (87410aa4c46953f015aae3a513cbe44db95033e13aac23e48e9f86c4ac482977)
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 (9608faee43a02423aaf69985bd63b5c9bd188dbfeccc359fb9de20cfdf432a7e)
The OpenSSF Package Analysis project identified 'sm-payment' @ 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.1
• 99.0.0

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