Skip to main content
POST
Analyze files that run during CI
Some campaigns leave workflows untouched and hide the payload in a file the workflow already runs: a postinstall script, conftest.py, setup.py or a Makefile target. This endpoint checks those files for:
  • Reading the token that actions/checkout stores, dumping the environment, and harvesting credential files
  • Install hooks that run hidden scripts
  • Workflows created or dispatched from build code, and forged commit statuses
  • Exfiltration endpoints, encoded or obfuscated code, and indicators from campaigns such as prt-scan and wfx-loot
Send the files a pull request adds or changes. The GitHub Action does this for you. Costs 2 units of your rate limit per request. Files are analyzed in memory and not stored.

Request

The body can be up to 256 KB.

Example

tests/conftest.py

Response

Finding

Errors

Body

application/json
files
object[]
required
Required array length: 1 - 10 elements

Response

CI files report

summary
object
required
files
object[]
required
findings
object[]
required