Which versions of conp-dats-editor are malicious?

The following npm versions of conp-dats-editor are flagged malicious: 999.999.990, 999.999.991, 999.999.992, 999.999.999. Treat any of these as compromised.

How do I remediate conp-dats-editor if I installed it?

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

If conp-dats-editor 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.

Is conp-dats-editor part of a known attack campaign?

Yes — conp-dats-editor is associated with the RLMA-2026-01218 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 conp-dats-editor across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for conp-dats-editor (4 malicious versions).

Malicious package

conp-dats-editornpm

Advisory published Feb 5, 2026Updated Mar 19, 2026

conp-dats-editor is a confirmed malicious npm package (MAL-2026-772) that executes malicious code on install (malicious versions 999.999.990, 999.999.991, 999.999.992…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in conp-dats-editor (npm)

MAL-2026-772

Immediate action

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

npm uninstall conp-dats-editor

What this malware does

The package conp-dats-editor was found to contain malicious code.

The OpenSSF Package Analysis project identified 'conp-dats-editor' @ 999.999.992 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

4 flagged

999.999.990999.999.991999.999.992999.999.999

Indicators of compromise (SHA-256)

5cc3fee45af6f0e407d38408a6aa3f93cdf57db282c56f1b96c216a1fdfc9c74

adac2b3e811707a0113ec1484330ebada12a632966c81143eab49233e87cabbf

4e47b3d8aefeb1ce047a36a4c96e01642d2dd39260f0c64b4b8dbe88bb891fb9

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for conp-dats-editor (4 malicious versions).
If you installed it — respond
Remove conp-dats-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 conp-dats-editor 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. conp-dats-editor on npm has been identified as a malicious package (versions 999.999.990, 999.999.991, 999.999.992, 999.999.999 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01218

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks conp-dats-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

Explore

All malware advisories How O3 detects malware Vulnerability database