# pentest-copilot - flagged on RubyGems

> The advisories that named pentest-copilot on RubyGems.org did not list releases, because it never had a legitimate one. There is no version to upgrade to: remove it outright. It is named in 1 tracked supply-chain incident. pentest-copilot was recorded in a daily advisory sweep. The write-up groups it into a cluster with the evidence available at the time; check the cluster note before treating it as a confirmed compromise.

- Package: pentest-copilot
- Ecosystem: RubyGems
- Highest severity: high
- Kind: Advisory sweep
- Compromised versions: none named (Flagged at package level: no release of this package is known good.)
- Check what you have installed: `gem list pentest-copilot`

## The incident that flagged it

| Date | Severity | Kind | Incident | Versions named |
|---|---|---|---|---|
| 2026-11-12 | high | Advisory sweep | [GitHub Advisory malware sweep, 12 November 2026](https://dependencywatch.io/incident/multi-2026-11-12-ghsa-malware-sweep) | no safe version |

## What to do if you installed one of these

1. Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.
2. Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a *different* machine.
3. Remove the dependency: no release is known good, so there is nothing to pin to. Reinstall from a clean lockfile.
4. Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
5. Read the incident write-up linked above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

## Check your whole project

We don't parse RubyGems manifests yet, but the incident write-ups list every affected package. Incident feed: https://dependencywatch.io/feed

All flagged RubyGems packages: https://dependencywatch.io/package/rubygems

## Other packages in the same incident

If pentest-copilot is in your tree, these are worth checking too - they were published by the same campaign.

- [@brunosps00/dev-workflow](https://dependencywatch.io/package/npm/@brunosps00/dev-workflow) (npm)
- [@budetzz/baileys](https://dependencywatch.io/package/npm/@budetzz/baileys) (npm)
- [@budetzz/eslint-config](https://dependencywatch.io/package/npm/@budetzz/eslint-config) (npm)
- [@budetzz/libsignal-node](https://dependencywatch.io/package/npm/@budetzz/libsignal-node) (npm)
- [@csp-frontend/auth](https://dependencywatch.io/package/npm/@csp-frontend/auth) (npm)
- [@csp-frontend/dashboard](https://dependencywatch.io/package/npm/@csp-frontend/dashboard) (npm)
- [@go-gost/mcp-darwin-x64](https://dependencywatch.io/package/npm/@go-gost/mcp-darwin-x64) (npm)
- [@hesxo/forge-cli](https://dependencywatch.io/package/npm/@hesxo/forge-cli) (npm)
- [@hesxo/viro-cli](https://dependencywatch.io/package/npm/@hesxo/viro-cli) (npm)
- [@ndikagantengg/baileys](https://dependencywatch.io/package/npm/@ndikagantengg/baileys) (npm)
- [@rclaude/darwin-x64](https://dependencywatch.io/package/npm/@rclaude/darwin-x64) (npm)
- [@rfewqa-fes/mnm-doc-mcp](https://dependencywatch.io/package/npm/@rfewqa-fes/mnm-doc-mcp) (npm)

Full incident: https://dependencywatch.io/incident/multi-2026-11-12-ghsa-malware-sweep

## Sourcing

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Corrections: https://dependencywatch.io/submit

---

Canonical page: https://dependencywatch.io/package/rubygems/pentest-copilot
Markdown version: https://dependencywatch.io/package/rubygems/pentest-copilot.md
Site index for agents: https://dependencywatch.io/llms.txt
DependencyWatch.io is operated by Precursor Security (https://precursorsecurity.com).