Documentation

Download, verify and run one program that checks this computer, a folder, a GitHub account or an organization for PolinRider.

How to check that polinrider came from this repository: signed commits, attested releases and SHA256SUMS on every release.

Releases up to 2.3.0 were built when the repository was called polinrider-cleaner. How to check one of them is genuine now that it is polinrider-scanner.

What each polinrider exit code means for scripts and CI: 0 clean, 1 review, 2 compromised and 3 could not run, and what to do after each one.

Scanner matches that look alarming but are harmless, each one confirmed during a real PolinRider cleanup, why they match and what to do about them.

Why PolinRider comes back after a cleanup, and the order that stops it: machines, credentials, repositories, then every future push.

Every step of a PolinRider cleanup on one checklist: infected computers, credentials, GitHub repositories and npm, and the checks still done by hand.

Check macOS, Linux or Windows for PolinRider with one read-only program, before you touch GitHub: infected files, persistence and an installed implant.

Check every branch and tag of every repository you own for PolinRider, see who pushed what from GitHub's push record, then restore or clean what was hit.

Check every repository, branch and tag in a GitHub organization for PolinRider, see who pushed what, then restore or clean every repository that was hit.

A PolinRider scanner you copy into your own repository, so every push and pull request is checked in CI, with no third-party action to trust.

How to report a missed PolinRider detection or a false positive, and how to propose a change to the scanner's code or to its indicator set.

How to report a vulnerability in the PolinRider scanner privately through GitHub Security Advisories, and where to report an infection instead.

Read before running: an independent open source project by one person, not a commercial product, and what that means for you.