Which versions of nifty-cli are malicious?

The following PyPI versions of nifty-cli are flagged malicious: 100.0.0. Treat any of these as compromised.

How do I remediate nifty-cli if I installed it?

nifty-cli is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed nifty-cli — how do I know if it already compromised me?

If nifty-cli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is nifty-cli part of a known attack campaign?

Yes — nifty-cli is associated with the RLMA-2025-01977, GENERIC-standard-pypi-install-pentest, RLUA-2026-00558 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 nifty-cli across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nifty-cli (version 100.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nifty-cli across your stack and pipelines.

Malicious package

nifty-cliPyPI

Malicious code in nifty-cli (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-2979

Immediate action

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

pip uninstall nifty-cli

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

100.0.0

Indicators of compromise (SHA-256)

2efc36cd6ee40277b3dedff42380c7695224f298acfeee807c80e80d861a6776

3c522808c412c85c29e9a591192df50905861d1deb76702170e54ca875c2472f

4b2e94e5fff47d4815f87f6dc9ba29b20022d6022c37e0b32ba9e3df81111eb5

f528235e07b142d0533e26c1a42dab602c22d474f342fa322ba67c3b8b744de9

8e1240a9a44391e6d4d9fb9613e2cdf049fc65a4a0b58a169847111ccf7e8be3

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nifty-cli (version 100.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nifty-cli across your stack and pipelines.
If you installed it — respond
nifty-cli is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If nifty-cli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks nifty-cli before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. nifty-cli on PyPI has been identified as a malicious package (version 100.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-01977GENERIC-standard-pypi-install-pentestRLUA-2026-00558

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks nifty-cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring