eslint-config-compact-utilsnpm
eslint-config-compact-utils is a confirmed malicious npm package (MAL-2026-16417) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in eslint-config-compact-utils (npm)
What this malware does
On require, index.js collects host reconnaissance data (os.hostname(), os.userInfo().username, os.platform(), architecture, Node version, current working directory) together with CI/repository environment variables (CI, RUNNER_NAME, GITHUB_REPOSITORY) and sends them as query parameters via https.get to the hardcoded endpoint https://cbrsuo9293.execute-api.us-east-1.amazonaws.com/c. The exfiltration fires as a side effect of importing the module and is unrelated to the package's advertised ESLint configuration purpose. The shape (import-time beacon carrying host identity plus CI/repo identifiers to a non-first-party AWS API Gateway) is consistent with dependency-confusion / typosquat reconnaissance.
The OpenSSF Package Analysis project identified 'eslint-config-compact-utils' @ 1.0.0 (npm) as malicious.
It is considered malicious because:
- The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eslint-config-compact-utils (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-config-compact-utils across your stack and pipelines.
If you installed it — respond
eslint-config-compact-utils 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 eslint-config-compact-utils 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 eslint-config-compact-utils 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
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks eslint-config-compact-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.