Which versions of windows_registry_editor are malicious?

The following npm versions of windows_registry_editor are flagged malicious: 0.0.1-security, 1.0.0. Treat any of these as compromised.

How do I remediate windows_registry_editor if I installed it?

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

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

How do I find windows_registry_editor across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for windows_registry_editor (2 malicious versions).

Malicious package

windows_registry_editornpm

Advisory published Oct 30, 2025Updated Oct 7, 2026

windows_registry_editor is a confirmed malicious npm package (MAL-2025-49244) that executes malicious code on install (malicious versions 0.0.1-security, 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in windows_registry_editor (npm)

MAL-2025-49244

Immediate action

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

npm uninstall windows_registry_editor

What this malware does

The package windows_registry_editor was found to contain malicious code.

Malicious versions

2 flagged

0.0.1-security1.0.0

Indicators of compromise (SHA-256)

b0bcad8f2c4bdd8438d2826d78f285454aa72dc719c9fb7d52a74928c5b999d0

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder

Detect & block this

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