Which versions of origin_response_handler are malicious?

Every published version of origin_response_handler on npm is considered malicious. Remove the package entirely.

How do I remediate origin_response_handler if I installed it?

Remove origin_response_handler 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.

I already installed origin_response_handler — how do I know if it already compromised me?

If origin_response_handler 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 origin_response_handler part of a known attack campaign?

Yes — origin_response_handler is associated with the GHSA-qxpp-qvj3-7mr5 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 origin_response_handler 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 origin_response_handler (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging origin_response_handler across your stack and pipelines.

Malicious package

origin_response_handlernpm

Malicious code in origin_response_handler (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-299

Immediate action

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

npm uninstall origin_response_handler

What this malware does

The package origin_response_handler 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.

Malicious versions

all versions

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

Indicators of compromise (SHA-256)

430f01e7a54ba6e13e0d26328d24c5fc2c743d67188653b4d61891fedb6dc68f

8faad8671b80a3e7c97ff0773ce270b02954a5f9152d1b06ab5d2af776fdc19d

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for origin_response_handler (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging origin_response_handler across your stack and pipelines.
If you installed it — respond
Remove origin_response_handler 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.
Did it already run?
If origin_response_handler 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 origin_response_handler 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. origin_response_handler on npm 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.

Campaign

GHSA-qxpp-qvj3-7mr5

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks origin_response_handler-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.

Malware detection Runtime egress monitoring