Which versions of Zendesk.Drivers are malicious?

The following NuGet versions of Zendesk.Drivers are flagged malicious: 23.0.8565, 23.0.8566, 23.0.8567, 23.0.8568. Treat any of these as compromised.

How do I remediate Zendesk.Drivers if I installed it?

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

If Zendesk.Drivers 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 Zendesk.Drivers part of a known attack campaign?

Yes — Zendesk.Drivers is associated with the RLMA-2024-03492 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 Zendesk.Drivers across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for Zendesk.Drivers (4 malicious versions).

Malicious package

Zendesk.DriversNuGet

Zendesk.Drivers is a confirmed malicious NuGet package (MAL-2024-4710) that executes malicious code on install (malicious versions 23.0.8565, 23.0.8566, 23.0.8567…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in Zendesk.Drivers (NuGet)

MAL-2024-4710

Immediate action

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

remove Zendesk.Drivers

Malicious versions

4 flagged

23.0.856523.0.856623.0.856723.0.8568

Indicators of compromise (SHA-256)

d2882bd5f342c1da2cb1623b0513743e92932cd03695f577bcfb510cb61063de

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for Zendesk.Drivers (4 malicious versions).
If you installed it — respond
Remove Zendesk.Drivers 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 Zendesk.Drivers 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. Zendesk.Drivers on NuGet has been identified as a malicious package (versions 23.0.8565, 23.0.8566, 23.0.8567, 23.0.8568 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-03492

Credits

ReversingLabs · finder

Detect & block this

O3 blocks Zendesk.Drivers-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