Which versions of hellodista are malicious?

The following PyPI versions of hellodista are flagged malicious: 0.1.0, 0.1.2. Treat any of these as compromised.

How do I remediate hellodista if I installed it?

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

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

Yes — hellodista is associated with the RLMA-2025-03613, 2025-07-0x9xnx 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 hellodista 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 hellodista (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hellodista across your stack and pipelines.

Malicious package

hellodistaPyPI

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

MAL-2025-5653

Immediate action

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

pip uninstall hellodista

What this malware does

Series of packages mostly with an obfuscated infostealer attempting to collect Chrome data. While discord webhook is usually set to an example, there are other, correct uploading URLs

Some of related packages only test partial malicious code, like webhooks from overwritten setup.py

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

Campaign: 2025-07-0x9xnx

Reasons (based on the campaign):

infostealer
obfuscation
exfiltration-browser-data
exfiltration-crypto
The package overrides the install command in setup.py to execute malicious code during installation.

The OpenSSF Package Analysis project identified 'hellodista' @ 0.1.2 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

0.1.00.1.2

Indicators of compromise (SHA-256)

3311ae2d4539920be4c0baaaa8587368a7c562bf75e9ec8a8b27fa42898f906f

cfaa0efa2c66eddd3954987b56498787b31acaaae397e9476f7295c649319d75

961a1dc182f3246147be4cd32a42789f1cfffb8cccb19dd7d66b6ae1e09ce58e

988e08e45c0c2fdbdf337e012d3930d14eedbe4add858a55cee2156849033b90

ea9a22b2cdd8bb2163a057349eecad0dace8d2f5e6b2df2c33a60e5f220ab2c6

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

Campaign

RLMA-2025-036132025-07-0x9xnx

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

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