Which versions of hellowornd are malicious?

The following npm versions of hellowornd are flagged malicious: 50.5.5, 50.5.7, 50.6.7. Treat any of these as compromised.

How do I remediate hellowornd if I installed it?

Remove hellowornd from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed hellowornd — how do I know if it already compromised me?

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

Yes — hellowornd is associated with the GHSA-4f9q-ffgq-5w82 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 hellowornd 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 hellowornd (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hellowornd across your stack and pipelines.

Malicious package

helloworndnpm

Malicious code in hellowornd (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4839

Immediate action

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

npm uninstall hellowornd

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'hellowornd' @ 50.6.7 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged

50.5.550.5.750.6.7

Indicators of compromise (SHA-256)

471a17ae224d51c0d02a6c44507ed74de69d100d7bffc7f37b93e98971433607

6958193f67c8d826750c29af3480e64891008ad6da92a4cdedae9be4a7d77884

84fe05b11d08b2d76dacf98f62ddf5585913f86904cc1353222e331000b7cc96

0e9b9637d126bc60120f015b0af88898fae5cf613a015fd572ab74d2554e6d7f

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hellowornd (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hellowornd across your stack and pipelines.
If you installed it — respond
Remove hellowornd from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If hellowornd 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 hellowornd 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. hellowornd on npm has been identified as a malicious package (versions 50.5.5, 50.5.7, 50.6.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4f9q-ffgq-5w82

References

github.com

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks hellowornd-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring