NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@hyperlook/telemetry-sdknpm

Advisory published Updated

@hyperlook/telemetry-sdk is a confirmed malicious npm package (MAL-2025-191234) that steals credentials and exfiltrates sensitive data (malicious version 1.0.19). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @hyperlook/telemetry-sdk (npm)

MAL-2025-191234
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @hyperlook/telemetry-sdk

What this malware does

The package @hyperlook/telemetry-sdk 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged
1.0.19

Indicators of compromise (SHA-256)

5121a317445c2c16838bf3ce994ee511a08459e506c42f910828851fc6daed98
04e340bea9f74622f608785c980b8c2f6d0652fd89834408d85febfda2dd8d26
fc89d8ae1e7f05dd930ed4c9173e00320153c6bb111324358e1c6f43bc07a1db

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @hyperlook/telemetry-sdk (version 1.0.19).

  2. If you installed it — respond

    @hyperlook/telemetry-sdk 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.

  3. Did it already run?

    If @hyperlook/telemetry-sdk was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @hyperlook/telemetry-sdk on npm has been identified as a malicious package (version 1.0.19 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r4v8-wfrc-5gj8

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @hyperlook/telemetry-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@hyperlook/telemetry-sdk (npm) malicious package — MAL-2025-191234 | O3 Security