# actions-cool/maintain-one-comment - compromised GitHub Actions versions

> actions-cool/maintain-one-comment on the GitHub Actions marketplace has 0 versions flagged in 1 tracked supply-chain incident. Only the exact versions listed below were named by the source advisories. actions-cool/maintain-one-comment is a legitimate package. Only the versions listed were malicious; other versions were not affected, but a lockfile that resolved to a listed version installed the payload.

- Package: actions-cool/maintain-one-comment
- Ecosystem: GitHub Actions
- Highest severity: critical
- Kind: Compromise
- Compromised versions: 

## The incident that flagged it

| Date | Severity | Kind | Incident | Versions named |
|---|---|---|---|---|
| 2026-05-19 | critical | Compromise | [actions-cool/issues-helper + maintain-one-comment - every tag retargeted to TeamPCP imposter commit](https://dependencywatch.io/incident/github-actions-2026-05-19-actions-cool-tag-hijack) |  |

## 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. Pin to a version not listed above, then 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 GitHub Actions manifests yet, but the incident write-ups list every affected package. Incident feed: https://dependencywatch.io/feed

All flagged GitHub Actions packages: https://dependencywatch.io/package/github-actions

## Other packages in the same incident

If actions-cool/maintain-one-comment is in your tree, these are worth checking too - they were published by the same campaign.

- [actions-cool/issues-helper](https://dependencywatch.io/package/github-actions/actions-cool/issues-helper) (GitHub Actions)

Full incident: https://dependencywatch.io/incident/github-actions-2026-05-19-actions-cool-tag-hijack

## 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/github-actions/actions-cool/maintain-one-comment
Markdown version: https://dependencywatch.io/package/github-actions/actions-cool/maintain-one-comment.md
Site index for agents: https://dependencywatch.io/llms.txt
DependencyWatch.io is operated by Precursor Security (https://precursorsecurity.com).