What does the fsspecc malware do?

Package uses the template from https://github.com/thegoodhackertv/malpip to explore building malicious PyPI packages. Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: SCRIPT_KIDDIE-thegoodhacker-paquete 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. - Package uses simple pre-prepared tools to create a low-quality malicious action.

Which versions of fsspecc are malicious?

The following PyPI versions of fsspecc are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate fsspecc if I installed it?

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

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

Yes — fsspecc is associated with the RLMA-2025-03011, SCRIPT_KIDDIE-thegoodhacker-paquete, RLUA-2026-00334 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 fsspecc 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 fsspecc (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fsspecc across your stack and pipelines.

Malicious package

fsspeccPyPI

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

MAL-2025-5114

Immediate action

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

pip uninstall fsspecc

What this malware does

Package uses the template from https://github.com/thegoodhackertv/malpip to explore building malicious PyPI packages.

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

Campaign: SCRIPT_KIDDIE-thegoodhacker-paquete

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.
Package uses simple pre-prepared tools to create a low-quality malicious action.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

0bf7d65f1bc69043898efa574631953ebc06a497cbaf4dde990b86146ecba808

f99cdeeda5b92888abe92dd0fca7cc276f5673abce44295672331bc41c1805b0

90f4ad6035c504be5b282397b9a981d39fe71dcb0165be3b5d0571ac6274b51c

c5c6cc6e8bbf9026e89ce89e81a96c1c9b081ba239a6a00d4f952a14760657a4

3db8b477ebe786286241d20dac49d44cfd9972cf58c3256663f049e133df2719

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 fsspecc (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fsspecc across your stack and pipelines.
If you installed it — respond
fsspecc 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 fsspecc 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 fsspecc 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. fsspecc on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-03011SCRIPT_KIDDIE-thegoodhacker-paqueteRLUA-2026-00334

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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