Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

de-morgannpm

Advisory published Updated

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)

MAL-2026-14264
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall de-morgan

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.

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
2.1.3

Indicators of compromise (SHA-256)

93cdcef4435e4bbb8f5841076c9294b934eaebd268286204a37cab9c334a045f
a4d1b017307cd94adf58ca67afc495bca4be5b06323278db3a4539dea81b050d

Detection & response playbook

Typosquat
  1. Find it

    Search your lockfiles and build artifacts for de-morgan (version 2.1.3).

  2. 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.

  3. Did it already run?

    If de-morgan 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. de-morgan on npm has been identified as a malicious package (version 2.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018379GHSA-2vc2-gwg3-2gpx

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.

Explore

de-morgan (npm) malicious package — MAL-2026-14264 | O3 Security