# Malware case files and threat actors

The Resolve Platform's malware case file and threat actor profile: whether a malicious package or its author reached you, its indicators, and who is behind it.

Two Resolve Platform pages open from **Findings › Malware** (`/resolve/malware`) when you need the full story behind one malicious package or one author. The **malware case file** (`/resolve/malware-threat`) is one malicious-package threat, in the order a responder needs it. The **threat actor** profile (`/resolve/threat-actor`) is one author across the whole catalogue.

The Malware page itself, and how malware is detected, are covered in the [Malware](/malware.md) docs.

## Malware case file

Opened from a malware row or finding with the threat's identifier in the address (`?cveId=`). A rail jumps between the sections:

| Section | Answers |
|---|---|
| **Your exposure** | Whether the package is in your organisation: the repositories that include it, the installed versions, and when it was first detected. Each repository has a button that opens a Software Factory session to remove the package from it. |
| **What it does** | The threat description, and the raw payload description where the source has one |
| **Versions** | The affected version ranges, and **Safe harbour versions** to move to |
| **Delivery chain** | Packages this threat pulls in, or is pulled in by, to deliver its payload |
| **Indicators** | The indicators of compromise to hunt, each one copyable |
| **Threat actors** | Who is attributed, with the confidence and basis of each attribution, and a link to the actor's profile |
| **References** | References and evidence, including the OpenSourceMalware record where it is one of the sources |
| **Timeline** | Published, first and last seen by the feed, verified, and when it first reached your organisation |

When the package is not in any scanned repository or recorded SBOM, **Your exposure** says so. Where it is, the guidance is to remove it or move to a safe version, then rescan the repositories listed.

## Threat actor profile

Opened from an attribution on a case file, by actor id or by platform and handle. It answers three questions in order.

1. **Has this actor reached you?** The head says **Has reached your organisation** or **Not in your organisation**.
2. **What have they published?** Every threat the actor published across the whole catalogue, with severity and whether it is **Present** in your organisation. Filter to **All**, **In your organisation** or **Critical and high**, and search by id, package or registry.
3. **Who else is it?** **Accounts that share a signing key**, drawn as a graph. A key is a durable identity, so the same fingerprint under another handle links both accounts to one operator.

The profile also lists the actor's **Signing keys** and reputation signals from the public account (account created, followers, following, public repos, public gists, company, location, email). A sparse, new account is a stronger sign of a throwaway attacker than an established one.

## False positives

On the case file you can mark an indicator, or an actor attribution, as a false positive. The page asks you to confirm inline, and the decision can be undone straight after. Your organisation's findings that match become not affected. An indicator marked false positive is cleared for every Vulnesis customer. Read [Curation and indicators](/malware/guides/curation.md) before you mark one.

## Plan

Both pages need a signed-in account and work on every plan. The **Safe harbour versions** on a case file need **Pro** or above.

## Related

- [Malware curation](/malware/guides/curation.md) lists every decision your organisation has made.
- [Threat-intel definitions](/malware/guides/threat-intel.md) covers the indicator feeds `vulnetix malscan` uses offline.
