Which versions of getd-eslint-rules are malicious?

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

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

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

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

Yes — getd-eslint-rules is associated with the IN-MAL-2026-005215, IN-MAL-2026-005216, GHSA-jqwv-7cxv-rhvm, RLMA-2026-05542 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-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-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-eslint-rules across your stack and pipelines.

Malicious package

getd-eslint-rulesnpm

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

MAL-2026-5466

Immediate action

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

npm uninstall getd-eslint-rules

What this malware does

On npm install, postinstall.js collects host identifiers (os.hostname, os.userInfo username, os.platform, current working directory, CI environment variable, and package name/version) and sends them as query-string parameters in an HTTPS GET to a hardcoded webhook.site collector URL (postinstall.js line 18: https://webhook.site/18dc4281-d366-438a-9186-76fbcd56ade5?pkg=...&host=...&user=...&platform=...&cwd=...&ci=...). The fetch fires automatically on install and errors are silently swallowed. The package self-describes as a 'defensive typo-squat' research artifact, but installer-side identifiers are exfiltrated to a third-party request collector without consent regardless of stated intent. The package name pattern targets users who mistype an ESLint rules package, increasing the chance of unintended installation.

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)

17328047b2ec8dce82cfbdfd5b16c8f862d51dca26b02c9801587c220a48975a

d5100344ca21b9a5e78114686b9c4e94dc86e198d7407318be782e9a57c6d8b7

475d9167eb060364b156fd3187b6adcf907ef787757f600b94dcb312b505ee0c

8cda779021744901de29ceb6fa8d5e0e609f196740f4e3aa6cee987c94022ba2

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 getd-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-eslint-rules across your stack and pipelines.
If you installed it — respond
getd-eslint-rules 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 getd-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-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-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-005215IN-MAL-2026-005216GHSA-jqwv-7cxv-rhvmRLMA-2026-05542

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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