Which versions of OpenAI-Core are malicious?

The following NuGet versions of OpenAI-Core are flagged malicious: 1.3.1, 1.7.2, 1.7.3, 1.7.4, 1.7.5, 1.7.6, 1.7.7, 1.7.8, 1.7.9, 1.8.0, 1.8.1, 1.8.2, 1.8.5. Treat any of these as compromised.

How do I remediate OpenAI-Core if I installed it?

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

If OpenAI-Core 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 OpenAI-Core part of a known attack campaign?

Yes — OpenAI-Core is associated with the RLMA-2024-03390 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 OpenAI-Core across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for OpenAI-Core (13 malicious versions).

Malicious package

OpenAI-CoreNuGet

OpenAI-Core is a confirmed malicious NuGet package (MAL-2024-4602) that executes malicious code on install (malicious versions 1.3.1, 1.7.2, 1.7.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in OpenAI-Core (NuGet)

MAL-2024-4602

Immediate action

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

remove OpenAI-Core

Malicious versions

13 flagged

1.3.11.7.21.7.31.7.41.7.51.7.61.7.71.7.81.7.91.8.01.8.11.8.21.8.5

Indicators of compromise (SHA-256)

b0d70413223eada4e28c7dc922371a8678e69bca8905bfc66bc73ee3c6fce8e8

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for OpenAI-Core (13 malicious versions).
If you installed it — respond
Remove OpenAI-Core 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 OpenAI-Core 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. OpenAI-Core on NuGet has been identified as a malicious package (versions 1.3.1, 1.7.2, 1.7.3, 1.7.4, 1.7.5, 1.7.6, 1.7.7, 1.7.8, and 5 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-03390

Credits

ReversingLabs · finder

Detect & block this

O3 blocks OpenAI-Core-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