Which versions of getd-typescript-eslint-rules are malicious?

The following npm versions of getd-typescript-eslint-rules are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate getd-typescript-eslint-rules if I installed it?

getd-typescript-eslint-rules 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 getd-typescript-eslint-rules — how do I know if it already compromised me?

If getd-typescript-eslint-rules 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 getd-typescript-eslint-rules part of a known attack campaign?

Yes — getd-typescript-eslint-rules is associated with the IN-MAL-2026-005211, IN-MAL-2026-005212, GHSA-v3g3-ppm6-4vqp, RLMA-2026-05545 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 getd-typescript-eslint-rules 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 getd-typescript-eslint-rules (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 getd-typescript-eslint-rules across your stack and pipelines.

Malicious package

getd-typescript-eslint-rulesnpm

Malicious code in getd-typescript-eslint-rules (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5470

Immediate action

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

npm uninstall getd-typescript-eslint-rules

What this malware does

On npm install, the postinstall.js script collects the installer's hostname, OS username, platform, current working directory, CI environment markers (CI, BUILD_BUILDID, AGENT_NAME), and package name/version, then sends them as query parameters in an HTTPS GET to a hardcoded webhook.site collector (https://webhook.site/18dc4281-d366-438a-9186-76fbcd56ade5). Errors are swallowed so the install does not fail visibly. The package's own metadata declares it a typosquat targeting @getd/typescript-eslint-rules and frames the beacon as 'defensive security research,' but the on-install behavior identifies any installer (including internal CI build agents) to a third-party endpoint regardless of stated intent.

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)

caed4b0db34232c4ef920817b6087cee9ac0610ec4ec2e49edbb5f167342f42f

fbc75f9b06e69a7a9abfece2eb3d4f9c8b3c5f46e927b94c0037781e4aace47b

4bd0cf64b341cf3707367b4c054eddfc3676c9e180875927489e31ea28754c2a

0893c4a74f0dfc2d88df1f7f83ee4fdd27aff7f2695afdf7c20e5503dc3452c7

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 getd-typescript-eslint-rules (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 getd-typescript-eslint-rules across your stack and pipelines.
If you installed it — respond
getd-typescript-eslint-rules 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 getd-typescript-eslint-rules 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 getd-typescript-eslint-rules 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. getd-typescript-eslint-rules 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-005211IN-MAL-2026-005212GHSA-v3g3-ppm6-4vqpRLMA-2026-05545

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks getd-typescript-eslint-rules-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