Skip to content

Document the ScanMalware analyzer and its configuration #72

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jonaslejon wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Document the ScanMalware analyzer and its configuration #72

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
324ca8e
Document the ScanMalware analyzer and its configuration
jonaslejon Aug 29, 2026
71d46f5
Correct the ScanMalware request cost
jonaslejon Aug 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/IntelOwl/advanced_usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -253,6 +253,11 @@ To better understand how this integration works, here is a diagram showing how t

Some analyzers could require a special configuration:

- `ScanMalware`:
- `max_results` (default `20`): bounds how much a single run returns. It caps both the scan list and the Certificate Transparency domain list for an IP, which the API returns unlimited; when it applies, the response says so and keeps the real total.
- `fetch_scan_details` (default `true`): also fetch the risk verdict, indicators and AI classification for the most recent scan. Three extra requests per run (`/result`, `/ioc`, `/ai`); set it to `false` for a lighter lookup.
- `api_key_name` (optional): the API is anonymous, a key only raises the rate limit.

- `GoogleWebRisk`: this analyzer needs a service account key with the Google Cloud credentials to work properly.
You should follow the [official guide](https://cloud.google.com/web-risk/docs/quickstart) for creating the key.
Then you can populate the secret `service_account_json` for that analyzer with the JSON of the service account file.
Expand Down
1 change: 1 addition & 0 deletions docs/IntelOwl/usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -226,6 +226,7 @@ The following is the list of the available analyzers you can run out-of-the-box.
- `Quad9_DNS`: Retrieve current domain resolution with Quad9 DoH (DNS over HTTPS)
- `Quad9_Malicious_Detector`: Leverages Quad9 DoH to check if a domain is related to malware
- `Robtex`: scan a domain/IP against the Robtex Passive DNS DB
- `ScanMalware`: Look up a domain, URL or IP in the [ScanMalware](https://scanmalware.com) archive of sandboxed URL scans (no API key required)
- `Securitytrails`: scan an IP/Domain against [Securitytrails](https://securitytrails.com/) API
- `Shodan_Honeyscore`: scan an IP against [Shodan](https://www.shodan.io/) Honeyscore API
- `Shodan_Search`: scan an IP against [Shodan](https://www.shodan.io/) Search API
Expand Down