Which versions of heimdal-credentials are malicious?

The following PyPI versions of heimdal-credentials are flagged malicious: 2.1.0. Treat any of these as compromised.

How do I remediate heimdal-credentials if I installed it?

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

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

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

Malicious package

heimdal-credentialsPyPI

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

MAL-2026-1140

Immediate action

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

pip uninstall heimdal-credentials

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.1.0

Indicators of compromise (SHA-256)

44b549b64558430b61d35bb2eb2cfcf8ec15d75bacb38af8f34deafe5d6add2c

dc5440468dbe195642a1ef1f836ec185cb211900197d3fb5219e1a87c117ab1b

7db4e676f3598bf9a1f85f1e89bbc991e18d0e7ef1636bf1606d835175c482af

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

Campaign

2026-02-amigapythonupdaterRLMA-2026-00380RLUA-2026-01682

References

bad-packages.kam193.eu

Credits

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

Detect & block this

O3 blocks heimdal-credentials-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