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?

Remove getd-eslint-rules 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

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 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect getd-eslint-rules in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking getd-eslint-rules and packages like it before any post-install script runs.

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.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

17328047b2ec8dce82cfbdfd5b16c8f862d51dca26b02c9801587c220a48975a

d5100344ca21b9a5e78114686b9c4e94dc86e198d7407318be782e9a57c6d8b7

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-005216

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection