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

@testfei/hallo-wordnpm

Malicious code in @testfei/hallo-word (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191971
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @testfei/hallo-word

What this malware does

The package @testfei/hallo-word was found to contain malicious code.

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 '@testfei/hallo-word' @ 1.0.5 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

4 flagged
1.0.41.0.51.0.61.0.7

Indicators of compromise (SHA-256)

c47361f034c5d49f2e1961b84bb803de7cf2497ed0c56aea61ca3980e0a2ef95
f0875b81011bbe047a0974df19a0a0880fd5fb3ae773662b3f5cf63ebdd5d3f6
79743d47a23a6bb08420819842b6fc5231af618a9db690f117fd6e361c598559
2a3a7879534f97e19b353a2d62c81c5823b2a72a341233c9d96ce2816b6d483a
3c9dd2639f2dec69604a2db9f8a29b60abdc2a0cebadf7d83c0dcf939d8c9eba

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @testfei/hallo-word (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @testfei/hallo-word across your stack and pipelines.

  2. If you installed it — respond

    Remove @testfei/hallo-word 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.

  3. Did it already run?

    If @testfei/hallo-word 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 @testfei/hallo-word 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. @testfei/hallo-word on npm has been identified as a malicious package (versions 1.0.4, 1.0.5, 1.0.6, 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-pvc8-vm69-c9g2

References

Credits

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

Detect & block this

O3 blocks @testfei/hallo-word-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.