Which versions of FоrmЕditor are malicious?

The following NuGet versions of FоrmЕditor are flagged malicious: 1.3.2.1. Treat any of these as compromised.

How do I remediate FоrmЕditor if I installed it?

Remove FоrmЕditor 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 FоrmЕditor — how do I know if it already compromised me?

If FоrmЕditor 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 FоrmЕditor part of a known attack campaign?

Yes — FоrmЕditor is associated with the RLMA-2024-03274, RLMA-2026-00019 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 FоrmЕditor across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for FоrmЕditor (version 1.3.2.1).

Malicious package

FоrmЕditorNuGet

Advisory published Jun 25, 2024Updated Mar 19, 2026

FоrmЕditor is a confirmed malicious NuGet package (MAL-2024-4494) that executes malicious code on install (malicious version 1.3.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in FоrmЕditor (NuGet)

MAL-2024-4494

Immediate action

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

remove FоrmЕditor

Malicious versions

1 flagged

1.3.2.1

Indicators of compromise (SHA-256)

ec05305dfae92a206582dce08549531b4b2d1ff459ce99c256ccb8c96981d76a

50f59fe665bef65e3f9110ca16146c426ada3ea46fa2a9cac56a907778366452

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for FоrmЕditor (version 1.3.2.1).
If you installed it — respond
Remove FоrmЕditor 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 FоrmЕditor 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. FоrmЕditor on NuGet has been identified as a malicious package (version 1.3.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-03274RLMA-2026-00019

Credits

ReversingLabs · finder

Detect & block this

O3 blocks FоrmЕditor-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