Which versions of nagogy are malicious?

The following PyPI versions of nagogy are flagged malicious: 0.1.0, 0.1.1, 1.0.0, 1.1.0. Treat any of these as compromised.

How do I remediate nagogy if I installed it?

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

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

Yes — nagogy is associated with the RLMA-2024-04179, RLUA-2024-08552 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 nagogy across my projects, lockfiles, and CI pipelines?

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

Malicious package

nagogyPyPI

nagogy is a confirmed malicious PyPI package (MAL-2024-5397) that executes malicious code on install (malicious versions 0.1.0, 0.1.1, 1.0.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nagogy (PyPI)

MAL-2024-5397

Immediate action

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

pip uninstall nagogy

Malicious versions

4 flagged

0.1.00.1.11.0.01.1.0

Indicators of compromise (SHA-256)

34d699153b1e16d8ca27bfcfc3abc18b3deef67fa5852189ad06fed1a283ae14

f5756e611fbac4cf2ae989473c036745f8216921c516dcc9d88fa03b1449eed6

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for nagogy (4 malicious versions).
If you installed it — respond
Remove nagogy 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 nagogy 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. nagogy on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 1.0.0, 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04179RLUA-2024-08552

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks nagogy-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