What does the editorial-code malware do?

The OpenSSF Package Analysis project identified 'editorial-code' @ 99.0.1 (npm) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.

Which versions of editorial-code are malicious?

The following npm versions of editorial-code are flagged malicious: 99.0.1. Treat any of these as compromised.

How do I remediate editorial-code if I installed it?

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

If editorial-code 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 editorial-code across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for editorial-code (version 99.0.1).

Malicious package

editorial-codenpm

Advisory published May 27, 2026Updated May 27, 2026

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

Malicious code in editorial-code (npm)

MAL-2026-4830

Immediate action

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

npm uninstall editorial-code

What this malware does

The OpenSSF Package Analysis project identified 'editorial-code' @ 99.0.1 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99.0.1

Indicators of compromise (SHA-256)

d7404afc131a113ef01d7eb896439a8719bb0f1b8d67e491d53321fdd5981e97

Detection & response playbook

Malicious package

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

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks editorial-code-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