Which versions of fwk-amigapython are malicious?

The following PyPI versions of fwk-amigapython are flagged malicious: 2.13.0. Treat any of these as compromised.

How do I remediate fwk-amigapython if I installed it?

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

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

Yes — fwk-amigapython is associated with the 2026-02-amigapythonupdater, RLMA-2026-00340, RLUA-2026-01679 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 fwk-amigapython 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 fwk-amigapython (version 2.13.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fwk-amigapython across your stack and pipelines.

Malicious package

fwk-amigapythonPyPI

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

MAL-2026-1137

Immediate action

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

pip uninstall fwk-amigapython

What this malware does

During import, only in specific environments, a module containing code disguised as telemetry is imported. This code then exfiltrates sensitive environment variables and cloud tokens to a hardcoded location, as well as starts a job listening for commands to execute. Likely dependency confusion attempts

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

Campaign: 2026-02-amigapythonupdater

Reasons (based on the campaign):

exfiltration-generic
exfiltration-env-variables
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
dependency-confusion

Malicious versions

1 flagged

2.13.0

Indicators of compromise (SHA-256)

8b565888509e90341d144143aa8e323b0e295d74f3857af52d94930d9d03a30f

77cc0991dd523e68051d8cc334254ef7993cde26104efe3d49860de1fa2945bc

b254b93269864e22ca0aa7477dc10ba415a3b7c9db46b5e47add9a24cc11548c

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

Campaign

2026-02-amigapythonupdaterRLMA-2026-00340RLUA-2026-01679

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst
ReversingLabs · finder

Detect & block this

O3 blocks fwk-amigapython-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