Which versions of kimportsetup are malicious?

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

How do I remediate kimportsetup if I installed it?

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

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

Yes — kimportsetup is associated with the RLMA-2025-04783, 2025-08-k7eel, RLUA-2026-00453 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 kimportsetup 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 kimportsetup (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kimportsetup across your stack and pipelines.

Malicious package

kimportsetupPyPI

Malicious code in kimportsetup (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-47779

Immediate action

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

pip uninstall kimportsetup

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)

3baa76edb955effa46d731700bd92c30a3337f511dbec5d9bd5341c56a9c3a4d

beccbd1337184314cbc87ee435e27d3c9f98c6bade6ea9e7af6ec63a38679723

a47d013a723f0b30a2a2cc1aab8efa31259713d6c778bd9df2c679b0c415370e

c70468b2c1e1ac8034368a7d510200419f0fe6ac0eddcb2d9ba0d2649a788eb9

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 kimportsetup (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kimportsetup across your stack and pipelines.
If you installed it — respond
kimportsetup 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 kimportsetup 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 kimportsetup 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. kimportsetup 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-047832025-08-k7eelRLUA-2026-00453

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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