Which versions of eslint-config-zeallat-base are malicious?

The following npm versions of eslint-config-zeallat-base are flagged malicious: 1.0.4. Treat any of these as compromised.

How do I remediate eslint-config-zeallat-base if I installed it?

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

If eslint-config-zeallat-base 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 eslint-config-zeallat-base part of a known attack campaign?

Yes — eslint-config-zeallat-base is associated with the GHSA-f67v-pxvp-9p9v 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 eslint-config-zeallat-base 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 eslint-config-zeallat-base (version 1.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-config-zeallat-base across your stack and pipelines.

Malicious package

eslint-config-zeallat-basenpm

Malicious code in eslint-config-zeallat-base (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190772

Immediate action

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

npm uninstall eslint-config-zeallat-base

What this malware does

The package eslint-config-zeallat-base 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.4

Indicators of compromise (SHA-256)

1b6b1b328e6d7538d35679194c6cec4543d7fe1ccd66a25ff5b76f43f7cd032a

b28fe7c28614bd60fe323d92db35df502ed3c1c9076a708815031e1a78311c6e

7ab87d5e56f014c8cbb0074b224c7beb4646b89983e09936b54bc85c969d3b20

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 eslint-config-zeallat-base (version 1.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-config-zeallat-base across your stack and pipelines.
If you installed it — respond
eslint-config-zeallat-base 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-zeallat-base 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-zeallat-base 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. eslint-config-zeallat-base on npm has been identified as a malicious package (version 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-f67v-pxvp-9p9v

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks eslint-config-zeallat-base-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