Which versions of comstrap are malicious?

Every published version of comstrap on npm is considered malicious. Remove the package entirely.

How do I remediate comstrap if I installed it?

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

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

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

Malicious package

comstrapnpm

Malicious code in comstrap (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-278

Immediate action

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

npm uninstall comstrap

What this malware does

The package comstrap 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)

0fdbf1b29e6524cad706ce8d312446d5869b2fb6614892bf9a350ade6b66d3df

9c9cb6396bf07d4b55b2e600f0e19966c1141733ef266c323e5382e75d0e1b76

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 comstrap (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging comstrap across your stack and pipelines.
If you installed it — respond
Remove comstrap 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 comstrap 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 comstrap 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. comstrap 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-c5gp-pw42-2hxc

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks comstrap-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