Which versions of importsetup are malicious?

The following PyPI versions of importsetup are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate importsetup if I installed it?

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

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

Yes — importsetup is associated with the RLMA-2025-04776, 2025-08-k7eel, RLUA-2026-00423 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 importsetup across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for importsetup (version 0.1.1).

Part of a larger attack: 2025-08-k7eel published 31 malicious packages. See the full campaign →

Malicious package

importsetupPyPI

Advisory published Aug 21, 2025Updated Mar 19, 2026

importsetup is a confirmed malicious PyPI package (MAL-2025-47774) that steals credentials and exfiltrates sensitive data (malicious version 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in importsetup (PyPI)

MAL-2025-47774

Immediate action

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

pip uninstall importsetup

What this malware does

Importing the module downloads and executes widely recognized malware

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-08-k7eel

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

7aff4207776cc0d94c527ac4876c9d8dbafb193ac93c7cc575334d7c0d4158e0

d904110948b0d88a15b2495940fadc277e0dcf79bdaf9095f3c68f5c7b4e9df6

07d601622d7b27ef8baa4ec8ef05e06c283dd18ace0fba3a856f3a5adbdce69e

78183501f5340d304a296d70995d675161f8f6329c077b3009db9a3ebd8bfe56

Detection & response playbook

Credential / info stealer

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

Campaign

RLMA-2025-047762025-08-k7eelRLUA-2026-00423

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database