Which versions of 2CaptcһaAPІ are malicious?

The following NuGet versions of 2CaptcһaAPІ are flagged malicious: 1.10.1. Treat any of these as compromised.

How do I remediate 2CaptcһaAPІ if I installed it?

Remove 2CaptcһaAPІ 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 2CaptcһaAPІ — how do I know if it already compromised me?

If 2CaptcһaAPІ 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 2CaptcһaAPІ part of a known attack campaign?

Yes — 2CaptcһaAPІ is associated with the RLMA-2024-02778, RLMA-2026-00009 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 2CaptcһaAPІ across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for 2CaptcһaAPІ (version 1.10.1).

Malicious package

2CaptcһaAPІNuGet

Advisory published Jun 25, 2024Updated Mar 19, 2026

2CaptcһaAPІ is a confirmed malicious NuGet package (MAL-2024-3991) that executes malicious code on install (malicious version 1.10.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 2CaptcһaAPІ (NuGet)

MAL-2024-3991

Immediate action

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

remove 2CaptcһaAPІ

Malicious versions

1 flagged

1.10.1

Indicators of compromise (SHA-256)

cf2b09777c333112a71c2179abc5da8b371c08b0b3b9af38b84d5ae7944c2d52

ce25918f6e0cc557aa964a8c6c450d12932e94c2dab045cd18cf3376f987e510

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-02778RLMA-2026-00009

Credits

ReversingLabs · finder

Detect & block this

O3 blocks 2CaptcһaAPІ-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