Which versions of ckeditor5-ckbox are malicious?

The following npm versions of ckeditor5-ckbox are flagged malicious: 5.0.0. Treat any of these as compromised.

How do I remediate ckeditor5-ckbox if I installed it?

ckeditor5-ckbox establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed ckeditor5-ckbox — how do I know if it already compromised me?

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

Yes — ckeditor5-ckbox is associated with the IN-MAL-2026-019147 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 ckeditor5-ckbox 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 ckeditor5-ckbox (version 5.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ckeditor5-ckbox across your stack and pipelines.

Malicious package

ckeditor5-ckboxnpm

ckeditor5-ckbox is a confirmed malicious npm package (MAL-2026-15549) that opens a backdoor for remote access (malicious version 5.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ckeditor5-ckbox (npm)

MAL-2026-15549

Immediate action

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

npm uninstall ckeditor5-ckbox

What this malware does

Unscoped npm package ckeditor5-ckbox mimics the legitimate @ckeditor/ckeditor5-ckbox plugin. package.json declares a preinstall hook (node index.js) that runs on npm install. index.js collects installer machine identifiers — os.hostname(), os.userInfo() (username, uid, gid, shell), platform/arch, home directory, cwd, and the output of whoami and id executed via child_process — and POSTs the JSON to the hardcoded Burp Collaborator OAST domain https://shdu19bid9mc4e6lezjmldk0erki88wx.oastify.com/system-info. The package contains no CKEditor functionality; the sole payload is the install-time beacon. Author/description are empty and the name is a typosquat of the scoped legitimate package.

Malicious versions

1 flagged

5.0.0

Indicators of compromise (SHA-256)

9373ed3aa6afb53ef5d5d3dd4860a4ed9e7b151fdd8c5c7782f2b2e914810fc7

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ckeditor5-ckbox (version 5.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ckeditor5-ckbox across your stack and pipelines.
If you installed it — respond
ckeditor5-ckbox establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If ckeditor5-ckbox 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 ckeditor5-ckbox 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. ckeditor5-ckbox on npm has been identified as a malicious package (version 5.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019147

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ckeditor5-ckbox-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database