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?

Remove getd-typescript-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-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 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-typescript-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-typescript-eslint-rules and packages like it before any post-install script runs.

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.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

caed4b0db34232c4ef920817b6087cee9ac0610ec4ec2e49edbb5f167342f42f

fbc75f9b06e69a7a9abfece2eb3d4f9c8b3c5f46e927b94c0037781e4aace47b

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

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