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

github.com/shadowybulk/hypertGo

Malicious code in github.com/shadowybulk/hypert (Go) Remove it immediately and rotate any exposed credentials.

MAL-2025-2547
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
remove github.com/shadowybulk/hypert

What this malware does

Malcious typosquatting Go packages targeting Linux and macOS systems used to as a loader to download and run another malicious payload.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

80a941bac0303482eb50ebe17fbfa05f22640a3932940be16100c6a1c0357a04

Detection & response playbook

Typosquat
  1. Find it

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

  2. If you installed it — respond

    github.com/shadowybulk/hypert is a typosquat — you almost certainly intended a legitimately-named package. Remove github.com/shadowybulk/hypert, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If github.com/shadowybulk/hypert 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 github.com/shadowybulk/hypert 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. github.com/shadowybulk/hypert on Go has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Socket · finder

Detect & block this

O3 blocks github.com/shadowybulk/hypert-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.

github.com/shadowybulk/hypert (Go) malicious package — MAL-2025-2547 | O3 Security