Which versions of chain-selectors are malicious?

The following npm versions of chain-selectors are flagged malicious: 2.0.0, 3.0.0, 4.0.0. Treat any of these as compromised.

How do I remediate chain-selectors if I installed it?

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

If chain-selectors 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 chain-selectors part of a known attack campaign?

Yes — chain-selectors is associated with the GHSA-2p37-4g2g-f26j 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 chain-selectors 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 chain-selectors (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chain-selectors across your stack and pipelines.

Malicious package

chain-selectorsnpm

Malicious code in chain-selectors (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191487

Immediate action

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

npm uninstall chain-selectors

What this malware does

The package chain-selectors 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.

The OpenSSF Package Analysis project identified 'chain-selectors' @ 2.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged

2.0.03.0.04.0.0

Indicators of compromise (SHA-256)

8b6b919a709a15f294b010ff4a9a4c38c6663506ad52aed2906020e2e8e02b2e

d37cc4e633062b930468aa6d1c664b8d21895c90b0d2e8b5438847b5b2242bf1

f7a3d2d57601f36ddfd88715627f89b3dec14937b5fb79db861e918a9574d4f2

9fb7c7965dde4649d4adda7307f395134f22ed654c9a20b2c7dc9ea1b0c1dad9

5632dc92ff1221e72c077781c43c1482a1a40fd5c703f95dd209890a4aa79410

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

Campaign

GHSA-2p37-4g2g-f26j

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks chain-selectors-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