Which versions of dip.infrastructure are malicious?

The following NuGet versions of dip.infrastructure are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate dip.infrastructure if I installed it?

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

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

Yes — dip.infrastructure is associated with the RLMA-2026-06568 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 dip.infrastructure across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dip.infrastructure (version 99.0.0).

Malicious package

dip.infrastructureNuGet

Advisory published Sep 22, 2026Updated Sep 24, 2026

dip.infrastructure is a confirmed malicious NuGet package (MAL-2026-16488) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dip.infrastructure (NuGet)

MAL-2026-16488

Immediate action

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

remove dip.infrastructure

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

a734cb6a43c1266cab2f8affb66aa90c71bd788c2a9d203ddc18440f27e40808

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-06568

Credits

ReversingLabs · finder

Detect & block this

O3 blocks dip.infrastructure-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