Which versions of coopshares-webcomponent are malicious?

Every published version of coopshares-webcomponent on npm is considered malicious. Remove the package entirely.

How do I remediate coopshares-webcomponent if I installed it?

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

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

Yes — coopshares-webcomponent is associated with the GHSA-pv7x-9f66-mjm7 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 coopshares-webcomponent 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 coopshares-webcomponent (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging coopshares-webcomponent across your stack and pipelines.

Malicious package

coopshares-webcomponentnpm

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

MAL-2026-413

Immediate action

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

npm uninstall coopshares-webcomponent

What this malware does

The package coopshares-webcomponent 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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

6d68cec4570dee0685b817d87e252fe045d2d03b44e5df960a06584ab5df1554

1a2f65589819f3e12665d8524a5db477f2c222a83ed178b584e7cf8e5901ead2

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

Campaign

GHSA-pv7x-9f66-mjm7

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks coopshares-webcomponent-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