ScanMalware
Operate ScanMalware through your OOMOL-connected account. This skill calls the scanmalware connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.
Running an action
ScanMalware needs no account connection. Assume the oo CLI is installed and signed in. Do not run oo auth login proactively — just run the action. Fall back to First-time setup only when a command actually fails.
1. Inspect the contract to get the authoritative input/output schema before building a payload:
oo connector schema "scanmalware" --action "<action_name>"
2. Run the action with a JSON payload that matches the input schema:
oo connector run "scanmalware" --action "<action_name>" --data '<json>' --json
--data takes a JSON object string or @path/to/file.json; omit it to send {}.
- The response is
{ "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.
Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action’s live schema with oo connector schema to get its authoritative input fields.
Available actions
get_domain_dns — Get the subdomains and IP addresses observed for a domain from Certificate Transparency logs and DNS resolution.
get_domain_scans — List recent public scans of a domain and its subdomains, or of an IP address. A scan whose matched_on contains url was submitted for this domain. A scan matched only on final_url started at another site that redirected here, often a phishing page imitating this domain, so its verdict describes that other site, not this domain.
get_scan_summary — Get the status, security verdict and risk score of one scan. The verdict describes the submitted url as it rendered at final_url, not every site that redirects there. security_verdict can stay empty for a few minutes after the status turns completed; read the summary again if it is empty.
search_scans — Search public scans with the ScanMalware query language, for example domain:example.com, ip:203.0.113.10, asn:13335, jarm:<fingerprint>, favicon_hash:<mmh3>, technology:WordPress, ct_domain:example.com or submitted:last7d, combined with AND, OR, NOT and parentheses. domain: and url: also match the final URL after redirects, so results can be other sites that redirect to the queried domain.
submit_scan — Submit a URL to be rendered and analyzed in a sandboxed browser. Returns a scan id; poll get_scan_summary until the status is completed or failed. [write]
Safety
- Untagged actions are reads (get / list / search) — safe to run directly.
- Actions tagged
[write] change ScanMalware state — confirm the exact payload and effect with the user before running.
- Actions tagged
[destructive] remove or overwrite data — always confirm the target and get explicit approval first.
First-time setup
These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.
-
oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux
irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell
-
Not signed in / authentication error — sign in to your OOMOL account once:
oo auth login
-
HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.
Resources
---
name: oo-scanmalware
description: "ScanMalware (scanmalware.com). Use this skill for ANY ScanMalware request — reading, creating, and updating data. Whenever a task involves ScanMalware, use this skill instead of calling the API directly."
allowed-tools: [Bash(oo *)]
metadata:
title: "ScanMalware"
author: "OOMOL"
version: "1.0.0"
services: ["scanmalware"]
icon: "https://static.oomol.com/logo/third-party/scanmalware.svg"
---
# ScanMalware
Operate **ScanMalware** through your OOMOL-connected account. This skill calls the `scanmalware` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.
## Running an action
ScanMalware needs no account connection. Assume the oo CLI is installed and signed in. **Do not run `oo auth login` proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails.
**1. Inspect the contract** to get the authoritative input/output schema before building a payload:
```bash
oo connector schema "scanmalware" --action "<action_name>"
```
**2. Run the action** with a JSON payload that matches the input schema:
```bash
oo connector run "scanmalware" --action "<action_name>" --data '<json>' --json
```
- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.
- The response is `{ "data": ..., "meta": { "executionId": "..." } }`; the execution id lives under `meta.executionId`.
Each action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.
## Available actions
- `get_domain_dns` — Get the subdomains and IP addresses observed for a domain from Certificate Transparency logs and DNS resolution.
- `get_domain_scans` — List recent public scans of a domain and its subdomains, or of an IP address. A scan whose matched_on contains url was submitted for this domain. A scan matched only on final_url started at another site that redirected here, often a phishing page imitating this domain, so its verdict describes that other site, not this domain.
- `get_scan_summary` — Get the status, security verdict and risk score of one scan. The verdict describes the submitted url as it rendered at final_url, not every site that redirects there. security_verdict can stay empty for a few minutes after the status turns completed; read the summary again if it is empty.
- `search_scans` — Search public scans with the ScanMalware query language, for example domain:example.com, ip:203.0.113.10, asn:13335, jarm:<fingerprint>, favicon_hash:<mmh3>, technology:WordPress, ct_domain:example.com or submitted:last7d, combined with AND, OR, NOT and parentheses. domain: and url: also match the final URL after redirects, so results can be other sites that redirect to the queried domain.
- `submit_scan` — Submit a URL to be rendered and analyzed in a sandboxed browser. Returns a scan id; poll get_scan_summary until the status is completed or failed. [write]
## Safety
- Untagged actions are reads (get / list / search) — safe to run directly.
- **Actions tagged `[write]` change ScanMalware state — confirm the exact payload and effect with the user before running.**
- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**
## First-time setup
These are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.
- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):
```bash
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux
```
```powershell
irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell
```
- **Not signed in / authentication error** — sign in to your OOMOL account once:
```bash
oo auth login
```
- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.
## Resources
- ScanMalware homepage: https://scanmalware.com