Which versions of priority-mutex-lane are malicious?

The following npm versions of priority-mutex-lane are flagged malicious: 2.5.1. Treat any of these as compromised.

How do I remediate priority-mutex-lane if I installed it?

Remove priority-mutex-lane from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed priority-mutex-lane — how do I know if it already compromised me?

If priority-mutex-lane 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 priority-mutex-lane part of a known attack campaign?

Yes — priority-mutex-lane is associated with the GHSA-fx8h-qw3r-xvf3, IN-MAL-2026-017797 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 priority-mutex-lane across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for priority-mutex-lane (version 2.5.1).

Malicious package

priority-mutex-lanenpm

Advisory published Aug 13, 2026Updated Aug 14, 2026

priority-mutex-lane is a confirmed malicious npm package (MAL-2026-14006) that executes malicious code on install (malicious version 2.5.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in priority-mutex-lane (npm)

MAL-2026-14006

Immediate action

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

npm uninstall priority-mutex-lane

What this malware does

The package was found to contain malicious code or consuming dependency that contains 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.

Malicious versions

1 flagged

2.5.1

Indicators of compromise (SHA-256)

79da50f5f1ef8bf4f49f3d9a0d9f073c25fa04f166311b0acf26320845498142

4bd0cb794e1b53c6b4c63bdd456196771029c0c003a33694581dadd3707acf0e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for priority-mutex-lane (version 2.5.1).
If you installed it — respond
Remove priority-mutex-lane from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If priority-mutex-lane 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. priority-mutex-lane on npm has been identified as a malicious package (version 2.5.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fx8h-qw3r-xvf3IN-MAL-2026-017797

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks priority-mutex-lane-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database