Which versions of gethandler-api are malicious?

The following npm versions of gethandler-api are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate gethandler-api if I installed it?

gethandler-api establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed gethandler-api — how do I know if it already compromised me?

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

Yes — gethandler-api is associated with the IN-MAL-2026-005209, IN-MAL-2026-005210, GHSA-92ff-fv46-jh35, RLMA-2026-05548 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 gethandler-api 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 gethandler-api (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gethandler-api across your stack and pipelines.

Malicious package

gethandler-apinpm

Malicious code in gethandler-api (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5473

Immediate action

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

npm uninstall gethandler-api

What this malware does

On npm install, postinstall.js unconditionally sends an HTTPS GET to https://webhook.site/18dc4281-d366-438a-9186-76fbcd56ade5 carrying the installer's hostname (os.hostname()), username (os.userInfo().username), platform (os.platform()), current working directory, package name/version, CI environment indicators, and a timestamp. Errors are silently swallowed so the install never visibly fails. The package.json self-describes as a 'defensive typo-squat' placeholder for the @getd/* namespace, but regardless of stated intent the behavior is non-consensual install-time transmission of installer identifiers to a third-party request-capture service. Anyone with the webhook URL — including the operator and anyone they share captures with — receives a log of every machine that fat-fingers an install of this name. The typosquat framing combined with the beacon means installers who mistype the target name are silently fingerprinted.

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

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0b6925d4c07df297f8cb573df4d85a396794d8793179e7a97f2cfde3aadfcfbc

ea0b26e761c1eb184707d6e8b06e844515bef1de5b38df98f95ba8af16c5a25f

2c94454c4670af273244b0a0a5d616bc72d86e2667757f6eae4f42bf59fcf46e

e3240bee9ddf1128c1a4deb12f3a8fcb658df21859a6b448dc3704c077f140a4

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for gethandler-api (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gethandler-api across your stack and pipelines.
If you installed it — respond
gethandler-api establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If gethandler-api 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 gethandler-api 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. gethandler-api on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005209IN-MAL-2026-005210GHSA-92ff-fv46-jh35RLMA-2026-05548

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks gethandler-api-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database