Which versions of fkask are malicious?

The following PyPI versions of fkask are flagged malicious: 3.1.8.dev0. Treat any of these as compromised.

How do I remediate fkask if I installed it?

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

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

Yes — fkask is associated with the RLMA-2025-00464, 2024-12-reqesst, RLUA-2026-00326 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 fkask 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 fkask (version 3.1.8.dev0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fkask across your stack and pipelines.

Malicious package

fkaskPyPI

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

MAL-2025-925

Immediate action

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

pip uninstall fkask

What this malware does

Importing the module downloads and starts an infostealer attempting to exfiltrate data and establishing persistence through autorun directory.

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

Campaign: 2024-12-reqesst

Reasons (based on the campaign):

infostealer
peristence-autorun
typosquatting
exfiltration-generic
Downloads and executes a remote executable.
clones-real-package
dependency-confusion
exfiltration-browser-data
exfiltration-crypto

Malicious versions

1 flagged

3.1.8.dev0

Indicators of compromise (SHA-256)

b4930756e2b05ca1620f71278c0f6d077ddaaac641368d2445bd1fa87e2a1830

a376a88b7a918549016d4e5c14f26ee85d6e7cecdd1f00f746d37f81dac6f8d3

d3bbbce78f8816ead148780776c4371cdd08775ee74639fea33b9598f8bb4b2b

5dec60f75d579194609a57b3de91581ecbe129db8011f71ff48aff9ca49e2317

6ac69d74914f3126b5ec2a4eafcc2c3fed5dccdf0662c72ef96576c8f21a7c01

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

Campaign

RLMA-2025-004642024-12-reqesstRLUA-2026-00326

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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