Which versions of @accordproject/concerto-linter are malicious?

The following npm versions of @accordproject/concerto-linter are flagged malicious: 3.24.1. Treat any of these as compromised.

How do I remediate @accordproject/concerto-linter if I installed it?

@accordproject/concerto-linter 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 @accordproject/concerto-linter — how do I know if it already compromised me?

If @accordproject/concerto-linter 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 @accordproject/concerto-linter part of a known attack campaign?

Yes — @accordproject/concerto-linter is associated with the GHSA-jgmx-8q5r-q7fg 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 @accordproject/concerto-linter across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @accordproject/concerto-linter (version 3.24.1).

Part of a larger attack: @accordproject published 8 malicious packages. See the full campaign →

Malicious package

@accordproject/concerto-linternpm

Advisory published Nov 25, 2025Updated Dec 1, 2025

@accordproject/concerto-linter is a confirmed malicious npm package (MAL-2025-191172) that steals credentials and exfiltrates sensitive data (malicious version 3.24.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @accordproject/concerto-linter (npm)

MAL-2025-191172

Immediate action

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

npm uninstall @accordproject/concerto-linter

What this malware does

The package @accordproject/concerto-linter 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

3.24.1

Indicators of compromise (SHA-256)

9a125b90d9837ebf1ec00b5ff1ecc1820bf8cc4f8a24388e26601ee6692be0c5

08b6d4ffe72c25a8994384e0cdf9c58e312d35e33d1c7df91493316420e3836d

6a266ef73fe4cd4e7227a57de2c97b342daf2ae0aed81e06b41bd9a55ab02d24

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @accordproject/concerto-linter (version 3.24.1).
If you installed it — respond
@accordproject/concerto-linter 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 @accordproject/concerto-linter 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. @accordproject/concerto-linter on npm has been identified as a malicious package (version 3.24.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jgmx-8q5r-q7fg

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @accordproject/concerto-linter-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