Which versions of const-enum are malicious?

Every published version of const-enum on npm is considered malicious. Remove the package entirely.

How do I remediate const-enum if I installed it?

Remove const-enum 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 const-enum — how do I know if it already compromised me?

If const-enum 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 const-enum part of a known attack campaign?

Yes — const-enum is associated with the GHSA-pwjh-p895-7767 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 const-enum across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for const-enum (all published versions).

Malicious package

const-enumnpm

Advisory published Jan 7, 2026Updated Jan 8, 2026

const-enum is a confirmed malicious npm package (MAL-2026-103) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in const-enum (npm)

MAL-2026-103

Immediate action

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

npm uninstall const-enum

What this malware does

The package const-enum was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

b9e5e7ad6ed97cfa1d1a71c51090aa5350d5166494a11fa6e6c9bbdad50dfc28

9a75bfbf64070500e046f70ab9f4422cd37764182dfa1c2d841bdbff803b4e24

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for const-enum (all published versions).
If you installed it — respond
Remove const-enum 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 const-enum 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. const-enum on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-pwjh-p895-7767

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks const-enum-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