Which versions of semaphore-job-pool are malicious?

The following npm versions of semaphore-job-pool are flagged malicious: 2.2.2. Treat any of these as compromised.

How do I remediate semaphore-job-pool if I installed it?

Remove semaphore-job-pool 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 semaphore-job-pool — how do I know if it already compromised me?

If semaphore-job-pool 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 semaphore-job-pool part of a known attack campaign?

Yes — semaphore-job-pool is associated with the GHSA-m4rw-m6pc-rjrx, IN-MAL-2026-017796 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 semaphore-job-pool 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 semaphore-job-pool (version 2.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging semaphore-job-pool across your stack and pipelines.

Malicious package

semaphore-job-poolnpm

semaphore-job-pool is a confirmed malicious npm package (MAL-2026-14010) that executes malicious code on install (malicious version 2.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in semaphore-job-pool (npm)

MAL-2026-14010

Immediate action

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

npm uninstall semaphore-job-pool

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.2.2

Indicators of compromise (SHA-256)

ef49573ba54204ce61ed683ca12bf9f601f1193f354ad6aaad6ff505ab0ebefa

894dd3724c09345add605b1ec247a8b2780a964fe89316f23fc0e57266ac35d7

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for semaphore-job-pool (version 2.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging semaphore-job-pool across your stack and pipelines.
If you installed it — respond
Remove semaphore-job-pool 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 semaphore-job-pool 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 semaphore-job-pool 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. semaphore-job-pool on npm has been identified as a malicious package (version 2.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-m4rw-m6pc-rjrxIN-MAL-2026-017796

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks semaphore-job-pool-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