Which versions of shoots-flutter are malicious?

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

How do I remediate shoots-flutter if I installed it?

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

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

Yes — shoots-flutter is associated with the RLMA-2025-00528, 2024-11-0wn-sh, RLUA-2026-00757 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 shoots-flutter 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 shoots-flutter (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 shoots-flutter across your stack and pipelines.

Malicious package

shoots-flutterPyPI

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

MAL-2025-987

Immediate action

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

pip uninstall shoots-flutter

What this malware does

Importing the module triggers sending out the hostname to the package author. It looks to be a placeholder/pentest activity related to BytedDance.

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: 2024-11-0wn-sh

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.

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

e2debfc5446f35afefcfcef27badfe53ff26554acd9b86985a652fc949d64919

a739bffa640d790e00d93d8926daa6dd764f9aef5fcbd7cbf41e84a8ebf8afcc

6a612693cb09ca6ca66ccd908b99293ec9ade7b7a719b78f0743332cba338071

0285b1b379303f26d31504f704617e65d2b299142e8e9a159ed1b1349aef9d38

04bc0c2a8113c739df5ca089ca64e9960b9fd83f4863d91ffaedd7f5427ebcb0

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 shoots-flutter (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 shoots-flutter across your stack and pipelines.
If you installed it — respond
shoots-flutter 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 shoots-flutter 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 shoots-flutter 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. shoots-flutter 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-005282024-11-0wn-shRLUA-2026-00757

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks shoots-flutter-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