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

conp-dats-editornpm

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

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
  1. Find it

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

  2. 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.

  3. Did it already run?

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

  4. How O3 protects you

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

conp-dats-editor (npm) malicious package — MAL-2026-772 | O3 Security