Which versions of @content-editor/common are malicious?

The following npm versions of @content-editor/common are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate @content-editor/common if I installed it?

Remove @content-editor/common 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 @content-editor/common — how do I know if it already compromised me?

If @content-editor/common 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.

Is @content-editor/common part of a known attack campaign?

Yes — @content-editor/common is associated with the GHSA-wwc7-v7xr-q4pc, RLMA-2026-04702, RLUA-2026-05404 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 @content-editor/common across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @content-editor/common (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @content-editor/common across your stack and pipelines.

Malicious package

@content-editor/commonnpm

@content-editor/common is a confirmed malicious npm package (MAL-2026-6607) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @content-editor/common (npm)

MAL-2026-6607

Immediate action

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

npm uninstall @content-editor/common

What this malware does

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

99.9.1

Indicators of compromise (SHA-256)

af120addbb0e18e1202a82729c25dc190dba070fee695cc22bcb91c7eea6ad25

f385d7402a3f865a256e1f2f613511a8d63108a3a0baffbfb4ec28d7a807e89c

8119d56d80a285fed9487a9b633ede96375801430feb3c0ed6d47503e459c7e9

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @content-editor/common (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @content-editor/common across your stack and pipelines.
If you installed it — respond
Remove @content-editor/common 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 @content-editor/common 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 @content-editor/common 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

No. @content-editor/common on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wwc7-v7xr-q4pcRLMA-2026-04702RLUA-2026-05404

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @content-editor/common-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