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

richtext-editor-uinpm

richtext-editor-ui is a confirmed malicious npm package (MAL-2026-5852) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in richtext-editor-ui (npm)

MAL-2026-5852
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall richtext-editor-ui

What this malware does

On npm install, postinstall.js base64-decodes a hardcoded URL (https://www.jsonkeeper.com/b/7EBZP), fetches its body via axios, and pipes the response into a detached, unref'd node child process through stdin — running arbitrary attacker-supplied JavaScript on the installer's machine without consent. The URL constant is misleadingly named DEV_API_KEY to disguise its purpose, and jsonkeeper.com is an anonymous mutable paste host where the served payload can be changed at any time. The package metadata also does not match its name: description, keywords (lambda, publish, compose, modular), and an index.js error message referencing 'theta' indicate the package is a lure published under a richtext-editor-shaped name to attract installs unrelated to its real behavior.

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
1.0.0

Indicators of compromise (SHA-256)

cee2cf9a14eccb5f263c23441ee102710afc9d1d24e73bdda0156e3ab002bb6b
fe87b6998b0d91eb7eefb71e37d8145b5db79b79dd21bc1ffda10d56d64b6d16

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove richtext-editor-ui 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.

  3. Did it already run?

    If richtext-editor-ui 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.

  4. How O3 protects you

    O3 blocks richtext-editor-ui 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. richtext-editor-ui on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fgqx-cjm6-75x2IN-MAL-2026-006878

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks richtext-editor-ui-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