Which versions of lint-staged-imagemin are malicious?

The following npm versions of lint-staged-imagemin are flagged malicious: 1.3.1, 1.3.2. Treat any of these as compromised.

How do I remediate lint-staged-imagemin if I installed it?

lint-staged-imagemin 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 lint-staged-imagemin — how do I know if it already compromised me?

If lint-staged-imagemin 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 lint-staged-imagemin part of a known attack campaign?

Yes — lint-staged-imagemin is associated with the GHSA-fc55-r563-7xhq 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 lint-staged-imagemin 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 lint-staged-imagemin (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lint-staged-imagemin across your stack and pipelines.

Malicious package

lint-staged-imageminnpm

Malicious code in lint-staged-imagemin (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191124

Immediate action

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

npm uninstall lint-staged-imagemin

What this malware does

The package lint-staged-imagemin 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

2 flagged

1.3.11.3.2

Indicators of compromise (SHA-256)

6053f2c33a709d5098dd42b1a8e188a75b3b82957c33c651b7894bc1bcdfea21

7cef2d955806e9496424dccedda2babaf9d59552af218de476ce37eff802bf00

f8cfbe33b97d4e3997d348c9532c834715e755ea1d28a6b30f2276209d4f45db

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

Campaign

GHSA-fc55-r563-7xhq

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks lint-staged-imagemin-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