Which versions of amigapythonupdater are malicious?

The following PyPI versions of amigapythonupdater are flagged malicious: 3.1.0, 3.1.1. Treat any of these as compromised.

How do I remediate amigapythonupdater if I installed it?

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

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

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

Malicious package

amigapythonupdaterPyPI

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

MAL-2026-1136

Immediate action

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

pip uninstall amigapythonupdater

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

2 flagged

3.1.03.1.1

Indicators of compromise (SHA-256)

46cf32631436ddacf36a4984b254c10554b4e94c6099c5012a96ec3a7c5426a1

424b9e1378b3acc560f20206c797a80be92759e8a7e412930c28ae69cc4243ac

7610023da2e27888c3037bc9f56c846c5347ba33a91232e26cab5d5980d88535

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

Campaign

2026-02-amigapythonupdaterRLMA-2026-00061RLUA-2026-01676

References

bad-packages.kam193.eu

Credits

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

Detect & block this

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