> For the complete documentation index, see [llms.txt](https://docs.stepsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stepsecurity.io/github/malicious-files/findings.md).

# Findings

The **Findings** page lists the files in your repositories that matched a malicious file rule. One finding is one file path matched by one rule, across every version of that file.

To open it, select **Malicious Files** > **Findings** in the **GitHub** section of the left navigation.

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2FcMYLBionYklk7K7IdDEz%2FScreenshot%202026-10-27%20at%2016.14.27.png?alt=media&amp;token=8178960d-336d-4107-a8ec-22241063c8c2" alt=""><figcaption></figcaption></figure>

Findings are grouped into three tabs: **Active**, **Resolved**, and **Suppressed**.

For each finding, StepSecurity shows:

* **File:** the file name, with the number of versions of the file and the number of refs (branches, pull requests and tags) it appears in. Select the file name to open the file in GitHub.
* **Repository:** the repository that contains the file
* **Campaign:** the campaign the matching rule detects
* **Rule:** the rule that matched
* **Severity:** the severity of the matching rule
* **Status:** the status of the finding, for example `Active`

Use the search box to find findings by file path, commit hash or blob hash, and the **severity**, **Campaign** and **Rule** filters to narrow the list. Select **Export CSV** to download the findings as a Comma-Separated Values (CSV) file.

A finding becomes vanished once no branch, pull request or tag still contains the file. Vanished findings are kept for 180 days unless they are resolved or suppressed.

#### **Resolving or suppressing a finding**

Select the actions menu (**⋮**) at the end of a finding's row to change its status:

* **Resolve file:** resolves the file, including every version of it, and moves the finding to the **Resolved** tab. You can add an optional comment. Use this after you have removed the file from every branch, pull request and tag that contained it.

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2FQJdsYzwNvJ8lpp0Ewi4J%2FScreenshot%202026-11-03%20at%2022.13.27.png?alt=media&amp;token=d0a75dff-a686-4738-92ce-3ab41c70d9f4" alt=""><figcaption></figcaption></figure>

* **Suppress file:** suppresses the file, including every version of it, and moves the finding to the **Suppressed** tab. Use this for a file you have reviewed and do not need to act on, such as a test fixture that intentionally contains malicious indicators.

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2FdJO6jk9fey5xgUjZq9s2%2FScreenshot%202026-11-03%20at%2022.10.57.png?alt=media&amp;token=f490e373-39ab-434d-85b6-fe788d1619ef" alt=""><figcaption></figcaption></figure>

When you suppress a file, select a reason and optionally add a comment:

| Reason             | Meaning                                   |
| ------------------ | ----------------------------------------- |
| **False positive** | The file is not malicious                 |
| **Not applicable** | The file is not relevant                  |
| **Accepted risk**  | The risk has been reviewed and accepted   |
| **Used in tests**  | The file is not in production code        |
| **Will fix later** | The issue will be addressed in the future |

The **Suppressed** tab adds a **Reason** column showing the reason you selected, followed by your comment if you added one (for example, `False positive: Test comment`).

To reverse either action, open the **Resolved** or **Suppressed** tab and select the actions menu (**⋮**) on the finding's row to unresolve or unsuppress it. The finding returns to the **Active** tab.

New versions of a resolved or suppressed file keep that status until you unresolve or unsuppress it. A malicious version pushed later to the same file path does not return the finding to **Active**, so resolve or suppress a file only after you have confirmed it is safe or fully removed.

### Finding details

Select a finding's row to open its details panel.

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2Fsjsz2SDcin4ePI5U55JP%2FScreenshot%202026-10-27%20at%2016.18.29.png?alt=media&amp;token=8b993db0-ee77-40fb-98e1-5e6fafd86b44" alt=""><figcaption></figcaption></figure>

The panel shows:

* **Repository:** the repository that contains the file
* **Rule:** the rule that matched, with the revision that produced the finding
* **First seen** and **Last seen:** when StepSecurity first and most recently found the file
* **Versions:** the blob hash of each version of the file that matched, with the most recent marked **Latest**
* **Found in:** every ref that currently contains the file, for example `heads/main` for a branch or `pull/1/head` for a pull request. Use this list to find every branch, pull request and tag you need to clean up.
* **Rule checks:** each check in the rule, whether it matched, and the pattern it used
* **Occurrences:** each place the file was introduced, with a link to the commit, its author, and the commit date. Select the commit link to open the commit in GitHub.

### Responding to a finding

When a file is flagged:

1. Open the finding and use **Rule checks** to confirm which indicators matched.
2. Use **Occurrences** to identify the commit that introduced the file and the account that pushed it. Treat that account's credentials as potentially compromised.
3. Use **Found in** to remove the file from every branch, pull request and tag that contains it.
4. Identify developers who may have cloned the repository or checked out an affected ref, and check their machines. If you use Dev Machine Guard, review Malicious Files [Findings](https://docs.stepsecurity.io/developer-machines/malicious-files/findings.md) in Dev Machine Guard for the same campaign.
5. Rotate any credentials that were accessible from affected machines or workflows.
6. Once the file is removed and credentials are rotated, select **Resolve file** from the finding's actions menu.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stepsecurity.io/github/malicious-files/findings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
