de-morgannpm
de-morgan is a confirmed malicious npm package (MAL-2026-14264) that typosquats a legitimate package to trick installs (malicious version 2.1.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in de-morgan (npm)
What this malware does
package.json declares both a dependencies and devDependencies entry for de-morgan pointing at http://pack.nppacks.com/npm/de-morgan, a non-npm-registry host reached over plain HTTP with no version pin or integrity check. On npm install, npm fetches and installs whatever tarball is served from that URL into the dependency graph, executing any lifecycle scripts it contains. The visible index.js is a clone of babel-plugin-transform-define and carries a top-of-file comment stating This package use for Security Research Testing Purpose., but the shipped manifest wires in an attacker-controlled, mutable, plaintext delivery URL under a lookalike domain (nppacks.com), so the installed code path is whatever the remote host currently serves rather than the benign in-tree source.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for de-morgan (version 2.1.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging de-morgan across your stack and pipelines.
If you installed it — respond
de-morgan is a typosquat — you almost certainly intended a legitimately-named package. Remove de-morgan, 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 de-morgan 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 de-morgan 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 de-morgan-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.