Which versions of @chtijs/eslint-config are malicious?

The following npm versions of @chtijs/eslint-config are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate @chtijs/eslint-config if I installed it?

@chtijs/eslint-config 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 @chtijs/eslint-config — how do I know if it already compromised me?

If @chtijs/eslint-config was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @chtijs/eslint-config part of a known attack campaign?

Yes — @chtijs/eslint-config is associated with the GHSA-4c6h-33gm-vqcx 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 @chtijs/eslint-config across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @chtijs/eslint-config (version 1.0.1).

Malicious package

@chtijs/eslint-confignpm

Advisory published Nov 25, 2025Updated Dec 1, 2025

@chtijs/eslint-config is a confirmed malicious npm package (MAL-2025-191200) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @chtijs/eslint-config (npm)

MAL-2025-191200

Immediate action

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

npm uninstall @chtijs/eslint-config

What this malware does

The package @chtijs/eslint-config was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

7eb74950af4a11bd106107b381dd9138cb15256c964c3acb09d8cdb33ea1e695

e4ceda78a90280970df51365230c82bd604dd812853ca367ba3aafa7179e6760

d13d42ca03eebf6bafc9addea00583d377c625dfac5eaff226bc3b0a155788c8

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @chtijs/eslint-config (version 1.0.1).
If you installed it — respond
@chtijs/eslint-config 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 @chtijs/eslint-config was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @chtijs/eslint-config on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4c6h-33gm-vqcx

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @chtijs/eslint-config-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

Explore

All malware advisories How O3 detects malware Vulnerability database