# MAL-2026-6382: Malicious code in fkaks (PyPI)


- **Type:** Malicious package
- **Package:** `fkaks` (PyPI)
- **Published:** 24 Jun 2026

## What is MAL-2026-6382?

MAL-2026-6382 is a malicious package in fkaks, published on 24 Jun 2026. 

### Official description

fkaks 0.0.1 ships a setup.py that overrides the install and egg_info commands so that any `pip install` or `pip download` of the package unconditionally executes a curl POST to a hardcoded out-of-band collector at http://gjampdwmdjmppwedtkpbbdkq05f6iiz6r.oast.fun. The POST body is built by iterating the entire `os.environ` mapping (`env_vars_string = "&".join([f"{key}={value}" for key, value in env_vars.items()])`) and concatenating it with the output of `ps -elf`, harvesting whatever secrets the installer or CI host has in environment variables (cloud credentials such as AWS_*, GitHub/registry tokens, CI secrets, SSH agent paths) along with a full process listing. The transport is plaintext HTTP to an interactsh-style oast.fun subdomain — infrastructure typical of OOB exfiltration callbacks. The README's framing of the package as a demo of automatic code execution on pip install does not change the on-the-wire behavior: every installer is attacked.

During installation, the package exfiltrates env variables

---

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

Campaign: 2026-06-ip-rotat

Reasons (based on the campaign):

 - The package overrides the install command in setup.py to execute malicious code during installation.

 - exfiltration-env-variables

 - typosquatting

## What should I do about MAL-2026-6382?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-6382 is a malicious package: fkaks (PyPI). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-6382/ (Markdown: https://insights.sbomify.com/MAL-2026-6382/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-6382

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-6382/
Summaries are generated and may contain mistakes; the official description above is the record.