Which versions of datatables-editor are malicious?

Every published version of datatables-editor on npm is considered malicious. Remove the package entirely.

How do I remediate datatables-editor if I installed it?

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

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

Yes — datatables-editor is associated with the GHSA-q7mc-g6jm-8pjq 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 datatables-editor 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 datatables-editor (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging datatables-editor across your stack and pipelines.

Malicious package

datatables-editornpm

Malicious code in datatables-editor (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-12

Immediate action

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

npm uninstall datatables-editor

What this malware does

The package datatables-editor was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

ac14c14a0e1472b84944a2153607fa90a3d074098be58d2f6ffe586a5bf80846

346a57a1d4e6a43df3540b29b3a84bbcc97071f58a1b5aec9e69504ff31c3fbe

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 datatables-editor (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging datatables-editor across your stack and pipelines.
If you installed it — respond
Remove datatables-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 datatables-editor 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 datatables-editor 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. datatables-editor on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-q7mc-g6jm-8pjq

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

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