Which versions of niked are malicious?

The following PyPI versions of niked are flagged malicious: 1.0. Treat any of these as compromised.

How do I remediate niked if I installed it?

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

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

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

Search your lockfiles and build artifacts for niked (version 1.0).

Malicious package

nikedPyPI

niked is a confirmed malicious PyPI package (MAL-2024-5411) that executes malicious code on install (malicious version 1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in niked (PyPI)

MAL-2024-5411

Immediate action

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

pip uninstall niked

Malicious versions

1 flagged

1.0

Indicators of compromise (SHA-256)

b0e7153d54434dd94fb6899dc9f53b8a69e9fe1714a804873e741b4eedb1769c

24dc544d26e4062aa8c1e0910d70eb8941269499a0a8f6442732aa195055ddcb

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-04193RLUA-2024-08567

Credits

ReversingLabs · finder

Detect & block this

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