• AI-Agent
  • Ready to Run

Check File Hashes

Look up file reputation and alert your team to malicious results

Use this Agent instantly or customize it - no programming needed

Check a file hash and report its reputation
Reads
  • Hash check request
    Hash check request

    Your slash command supplies one file hash and a route for the private reply.

  • File reputation report
    File reputation report

    Your file report shows the latest analysis date and how many engines flagged the file.

  • Security alert channel
    Security alert channel

    You choose the team channel that receives malicious hash alerts.

  • Verdict rule
    Verdict rule

    Your chosen rule ranks malicious findings first, suspicious findings next, and clean reports last.

Security chat service
Security chat service

Your security chat service takes hash check requests, sends private replies, and posts malicious findings to your team.

Security chat service
Malware reputation service
Malware reputation service

Your malware reputation service returns the latest file report for a submitted MD5, SHA-1, or SHA-256 hash.

Acknowledge the request with a private checking message.
Writes
  • Checking message
    Checking message

    You see a private confirmation while the hash check runs.

Is the hash missing, malformed, or mixed with other text?YesNo
Explain the required MD5, SHA-1, or SHA-256 format.
Writes
  • Private hash result
    Private hash result

    Your reply shows the verdict, detection count, and report date when available. It explains invalid hashes, failed lookups, and failed team alerts.

Look up the latest file report for the normalized hash.
Did the file lookup fail or hit a rate limit?YesNo
Tell the analyst the lookup failed.
Writes
  • Private hash result
    Private hash result

    Your reply shows the verdict, detection count, and report date when available. It explains invalid hashes, failed lookups, and failed team alerts.

Is the file report missing or without usable engine results?YesNo
Reply with an Unknown verdict.
Writes
  • Private hash result
    Private hash result

    Your reply shows the verdict, detection count, and report date when available. It explains invalid hashes, failed lookups, and failed team alerts.

Send the verdict and alert the team if it is Malicious.
Writes
  • Private hash result
    Private hash result

    Your reply shows the verdict, detection count, and report date when available. It explains invalid hashes, failed lookups, and failed team alerts.

  • Malicious hash alert
    Malicious hash alert

    Your team sees the malicious hash, malicious engine count, and report date in the channel you chose.

This Agent waits for your /hash-check command, then validates the hash and looks up its reputation. It replies privately with a verdict and detection count. For malicious findings, it alerts your chosen security channel.

Modify Agent

Customize this Agent to fit your needs using natural language.

Start Agent for Free

Enter your email address and we will send you a secure link to continue.

Slack
Used as:
Show all Agents working with Slack
Google Drive
Used as:
Show all Agents working with Google Drive
Asana
Used as:
Show all Agents working with Asana
ClickUp
Used as:
Show all Agents working with ClickUp
Zoom
Used as:
Show all Agents working with Zoom
Google Contacts
Used as:
Show all Agents working with Google Contacts
Google Chat
Used as:
Show all Agents working with Google Chat

Made for your industry

Check File Hashes is made for businesses in these industries.

Made for your role

Check File Hashes is made for people in these roles.

Made for your department

Check File Hashes is made for people in these departments.

How Check File Hashes works

4 steps, in order, on every run.

  1. Validate the submitted hashAcknowledge the request in chat. Accept one MD5, SHA-1, or SHA-256 hash; explain format errors privately.
  2. Look up file reputationRetrieve the latest file report for a valid hash. Tell the analyst if the reputation service fails or limits requests.
  3. Return a private verdictApply the verdict rule and reply privately with detection counts and report date. Mark missing or unusable reports Unknown.
  4. Alert the security channelPost malicious hashes with their detection count and report date to your chosen channel. Tell the analyst if the alert fails.

How to Get Started

Connect your tools

Connect the tools you already use, such as Slack, Google Drive or Asana.

7 tools
Set your rules
  • Create a /hash-check slash command with a reachable HTTPS request URL, signing secret, and permission to post in the chosen security alert channel.
  • Connect a file-reputation API key and choose the security alert channel.
  • Use this verdict rule: any malicious engine means Malicious; otherwise any suspicious engine means Suspicious; otherwise a report with completed engine results means Clean (no detections); a missing report or no usable results means Unknown.
Launch the Agent

Use safe mode to approve every result before it goes out, or let the Agent run automatically.

FAQs

Frequently asked questions about the Check File Hashes:

Which file hashes can I check?

You can submit one MD5, SHA-1, or SHA-256 hash with /hash-check. You get a private format message for missing or invalid text.

What does a clean file hash check mean?

Clean means the report has completed engine results and no malicious or suspicious detections. It does not prove the file is safe.

What happens when a report is missing or the lookup fails?

You see Unknown when no report or usable results exist. If the service fails or limits requests, you get a lookup error without a risk verdict.

Who gets alerted for a malicious result?

You choose the security alert channel during setup. Your team sees the hash, malicious detection count, and report date there.

What happens when the Agent is unsure?

It stops and asks you. The Agent does not guess when it reaches a decision you have not approved.

Can I review its work?

Yes. Every run creates a plain-language log that you can review and export. Logs are kept for twelve months.

What happens if I cancel?

The Agent stops at the end of the billing month and its tool connections are removed. Your run logs remain available for twelve months.

Related Agents

Agents related to Check File Hashes

More ready-to-run Agents for connected work.