Which versions of hello-dynamic are malicious?

The following PyPI versions of hello-dynamic are flagged malicious: 0.1.0, 0.1.1, 0.1.2. Treat any of these as compromised.

How do I remediate hello-dynamic if I installed it?

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

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

Yes — hello-dynamic is associated with the GENERIC-standard-pypi-install-pentest, IN-MAL-2026-008865, IN-MAL-2026-008968 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 hello-dynamic 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 hello-dynamic (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hello-dynamic across your stack and pipelines.

Malicious package

hello-dynamicPyPI

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

MAL-2026-5518

Immediate action

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

pip uninstall hello-dynamic

What this malware does

hello-dynamic 0.1.2 is a near-empty package whose init.py only defines a hello() function printing 'Hello!'. Its setup.cfg declares a dependency_links entry pointing at a webhook.site UUID endpoint (https://webhook.site/56557fe9-5bcf-4f26-bed7-38f772525011/pypi/aliga-raison). webhook.site is a generic HTTP-callback inspector commonly used to receive beacon traffic. Modern pip ignores dependency_links, so installer harm is minimal in practice, but the artifact's shape — trivial code, no real functionality, install metadata pointing at a request-inspector endpoint named after a PyPI package — is consistent with a reconnaissance probe testing which installers still process dependency_links. No exfiltration, RCE, credential read, or persistence mechanism is present in the package code.

Package attempts to test exploitation via legacy dependency_links configuration

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

3 flagged

0.1.00.1.10.1.2

Indicators of compromise (SHA-256)

168dd7abca8ed812dcfb0119eaf80a2b05b186ee37a1e0c8f98e88f884a90602

bd498b2e70ac8f0a58221910520992cddb5e8994c821db69c9ceba6a9a4aaa8f

d1532f25a13ed2c77496e590acadc24df4fa7d063e707c53687143a7457e2d2e

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

Campaign

GENERIC-standard-pypi-install-pentestIN-MAL-2026-008865IN-MAL-2026-008968

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks hello-dynamic-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

Explore

All malware advisories How O3 detects malware Vulnerability database