sm-paymentnpm
sm-payment is a confirmed malicious npm package (MAL-2026-14399) that opens a backdoor for remote access (malicious versions 99.0.0, 99.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in sm-payment (npm)
What this malware does
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.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sm-payment (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sm-payment across your stack and pipelines.
If you installed it — respond
sm-payment establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If sm-payment was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks sm-payment before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks sm-payment-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.