Which versions of identityapi are malicious?

The following PyPI versions of identityapi are flagged malicious: 3.0.0. Treat any of these as compromised.

How do I remediate identityapi if I installed it?

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

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

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

Malicious package

identityapiPyPI

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

MAL-2026-1141

Immediate action

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

pip uninstall identityapi

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

3.0.0

Indicators of compromise (SHA-256)

45946e31faffbed940c8acb3656be0d5f25de7db36f58766cdac44a1e7d6150b

c55c631299437a327e3a9b7ec27602874a0888250e7c108490dfbe9be2822262

117eeae76b1aab00a4cab7a416ef6a1fc9ddb87e58bd5b01bdb82394a5075b39

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

Campaign

2026-02-amigapythonupdaterRLMA-2026-00419RLUA-2026-01684

References

bad-packages.kam193.eu

Credits

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

Detect & block this

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