Which versions of @trpc-rate-limiter/hono are malicious?

The following npm versions of @trpc-rate-limiter/hono are flagged malicious: 0.1.4. Treat any of these as compromised.

How do I remediate @trpc-rate-limiter/hono if I installed it?

@trpc-rate-limiter/hono 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.

I already installed @trpc-rate-limiter/hono — how do I know if it already compromised me?

If @trpc-rate-limiter/hono 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.

Is @trpc-rate-limiter/hono part of a known attack campaign?

Yes — @trpc-rate-limiter/hono is associated with the GHSA-qjrq-hrv7-m27w campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @trpc-rate-limiter/hono across my projects, lockfiles, and CI pipelines?

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

Malicious package

@trpc-rate-limiter/hononpm

Malicious code in @trpc-rate-limiter/hono (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191328

Immediate action

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

npm uninstall @trpc-rate-limiter/hono

What this malware does

The package @trpc-rate-limiter/hono 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

0.1.4

Indicators of compromise (SHA-256)

4ffe31071f96091e487995efe3382f28220125494ac4418dbcbce93bd61ea438

1a9fe07b50de3c4a02449d05f405029e3eb352edf281bb621ec13444ddb8b0ad

e86780189d32c5c6215833b83e8ff4274af92653c41f51d8cb8f9c1e5262bccf

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @trpc-rate-limiter/hono (version 0.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @trpc-rate-limiter/hono across your stack and pipelines.
If you installed it — respond
@trpc-rate-limiter/hono 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.
Did it already run?
If @trpc-rate-limiter/hono 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.
How O3 protects you
O3 blocks @trpc-rate-limiter/hono 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. @trpc-rate-limiter/hono on npm has been identified as a malicious package (version 0.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qjrq-hrv7-m27w

References

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring