Which versions of sonmors are malicious?

The following npm versions of sonmors are flagged malicious: 2.11.2. Treat any of these as compromised.

How do I remediate sonmors if I installed it?

sonmors is a typosquat — you almost certainly intended a legitimately-named package. Remove sonmors, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed sonmors — how do I know if it already compromised me?

If sonmors 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.

Is sonmors part of a known attack campaign?

Yes — sonmors is associated with the IN-MAL-2026-019725 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 sonmors across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sonmors (version 2.11.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sonmors across your stack and pipelines.

Malicious package

sonmorsnpm

sonmors is a confirmed malicious npm package (MAL-2026-16055) that typosquats a legitimate package to trick installs (malicious version 2.11.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sonmors (npm)

MAL-2026-16055

Immediate action

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

npm uninstall sonmors

What this malware does

Package sonmors ships a near-copy of the sonner React toast library and spoofs sonner's identity in package.json (author Emil Kowalski <[email protected]>, homepage sonner.emilkowal.ski, repository github.com/emilkowalski/sonner) while being published under a different name. The only functional divergence from sonner in the shipped dist/index.js is a top-level const getLogger = require('gloggo'); var logger = getLogger('Log'); and a logger.infO('useSonner') call inside the exported hook. require('gloggo') executes on every require('sonmors'), so any consumer who mistypes sonner as sonmors pulls in and runs whatever the companion gloggo package contains at library-load time. The payload lives in the transitive dependency rather than in this tarball; the lure is the impersonated identity and the near-perfect sonner clone.

Malicious versions

1 flagged

2.11.2

Indicators of compromise (SHA-256)

66e21634e32b7d24357ad667703da4ddeb42542ed9fc6a3ed28c7257d2e27fca

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sonmors (version 2.11.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sonmors across your stack and pipelines.
If you installed it — respond
sonmors is a typosquat — you almost certainly intended a legitimately-named package. Remove sonmors, 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 sonmors 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 sonmors 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

No. sonmors on npm has been identified as a malicious package (version 2.11.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019725

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks sonmors-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