Skip to content

Add NetAPI analyzer. Closes #4111 - #4149

Open
slavaolesik wants to merge 1 commit into
intelowlproject:developfrom
slavaolesik:netapi-analyzer
Open

slavaolesik wants to merge 1 commit into
intelowlproject:developfrom
slavaolesik:netapi-analyzer

Conversation

@slavaolesik

@slavaolesik slavaolesik commented Nov 14, 2026 •

Copy link
Copy Markdown

Description

Adds the NetAPI observable analyzer proposed in #4111 (thanks for assigning it to me). It checks an IP, a domain or a URL host against the NetAPI compromised feed with one request to https://netapi.com/api-json/?method=compromised-check&value=.... The API is free and needs no key (limits per client IP: 30 requests a minute, 1,000 a day).

  • IPs are answered from NetAPI's own honeypot network: listed now = the address attacked the sensors within the last 48 hours.
  • Domains are answered from merged public blocklists: listed now = seen within the last 24 hours. For a host with subdomains the service also tries the parent domains and names the entry that matched in matched_value.
  • A URL is reduced to its host.

DataModel:

  • listed now, matched on the observable itself: malicious, reliability 7
  • listed now, but the match is a parent domain: malicious, reliability 5 (shown as suspicious); www.<domain> matched on <domain> counts as the domain itself, since the feed stores domains without www.
  • listed in the past only, matched on the observable itself: malicious, reliability 3 (shown as suspicious)
  • listed in the past only through a parent domain, or never listed: no data model (the raw report still has the details), because neither says anything about this host

The block reason, the matched value and the first / last seen dates go to additional_info.

The analyzer is added to FREE_TO_USE_ANALYZERS. Docs PR: intelowlproject/docs#78

Analysis result

Observable 1.0.166.69 (IP), analyzer NetAPI only, status SUCCESS in 0.49 s.

NetAPI analyzer report in IntelOwl
Raw JSON
{
  "analyzer": "NetAPI",
  "observable": "1.0.166.69",
  "status": "SUCCESS",
  "report": {
    "note": "Seen in the compromised feed within the last 48 hours.",
    "type": "ip",
    "lists": {
      "page": "https://netapi.com/compromised-ips/",
      "current": "https://netapi.com/api2/?method=compromised&dataset_type=ip",
      "all_time": "https://netapi.com/api2/?method=compromised&dataset_type=ip-all"
    },
    "value": "1.0.166.69",
    "source": "NetAPI Nightwatch compromised IP feed, updated hourly (CC BY 4.0)",
    "last_seen": "2026-11-13 05:36:10 UTC",
    "registrar": null,
    "first_seen": "2026-11-03",
    "listed_now": true,
    "listed_ever": true,
    "block_reason": "NetAPI network sensors: service exploit",
    "matched_value": "1.0.166.69"
  },
  "data_model": {
    "evaluation": "malicious",
    "reliability": 7,
    "additional_info": {
      "last_seen": "2026-11-13 05:36:10 UTC",
      "first_seen": "2026-11-03",
      "listed_now": true,
      "block_reason": "NetAPI network sensors: service exploit",
      "matched_value": "1.0.166.69"
    }
  }
}

Type of change

  • New feature (non-breaking change which adds functionality).

Checklist

  • I have read and understood the rules about how to Contribute to this project
  • The pull request is for the branch develop
  • A new plugin (analyzer, connector, visualizer, playbook, pivot or ingestor) was added or changed, in which case:
    • I strictly followed the documentation "How to create a Plugin"
    • Usage file was updated. A link to the PR to the docs repo has been added as a comment here.
    • Advanced-Usage was updated: not needed, the analyzer has no parameters.
    • I have dumped the configuration from Django Admin using the dumpplugin command and added it in the project as a data migration (0203_analyzer_config_netapi, after 0202_analyzer_config_scan_malware; the dumped config is identical, formatted with Ruff in the layout of the latest plugin migration).
    • If a File analyzer was added: not applicable.
    • If you created a new analyzer and it is free (does not require any API key), please add it in the FREE_TO_USE_ANALYZERS playbook (migration 0069_add_netapi_to_free_to_use).
    • Check if it could make sense to add that analyzer/connector to other freely available playbooks: I left the other playbooks alone; happy to add it where you think it fits.
    • I have provided the resulting raw JSON of a finished analysis and a screenshot of the results (above: a local instance built from this branch with the CI compose files, analyzer run on a listed IP).
    • If the plugin interacts with an external service, I have created an attribute called precisely url that contains this information.
    • If a new analyzer has beed added, I have created a unittest for it in the appropriate dir. I have also mocked all the external calls, so that no real calls are being made while testing.
    • I have added that raw JSON sample to the get_mocker_response() method of the unittest class.
    • I have created the corresponding DataModel for the new analyzer following the documentation
  • I have inserted the copyright banner at the start of the file.
  • Please avoid adding new libraries as requirements whenever it is possible: no new libraries.
  • If external libraries/packages with restrictive licenses were added: not applicable.
  • Linters (Ruff) gave 0 errors (ruff 0.14.10, the version pinned in .pre-commit-config.yaml: ruff check and ruff format --check on the new files).
  • I have added tests for the feature/bug I solved (see tests folder). All the tests (new and old ones) gave 0 errors: not all of them. The 12 new tests pass in the container, and real runs on a listed domain, its www. host, a subdomain, a URL, a past listing, a subdomain of a past listing, a clean domain and a clean IP give the verdicts listed above. The full tests suite ran with 1072 tests; the only failures (51) are tests that need the sample files of tests/test_files.zip, which I did not extract on my machine (Windows Defender quarantines them), so those files were empty. No failure touches this change. async_tests failed on my setup with a kombu / redis-py version mismatch, unrelated as well.
  • If the GUI has been modified: not applicable.
  • After you had submitted the PR, if DeepSource, Django Doctors or other third-party linters have triggered any alerts during the CI checks, I have solved those alerts.
  • I have addressed raised Copilot issues.
  • I have reviewed and verified any LLM-generated code included in this PR. Also, I have explicitly stated that I have used LLMs in this PR: the code and the tests were written with the help of an LLM (Claude), then reviewed and checked as described above.

Thanks!
Slava

Disclosure: I run NetAPI, the service this analyzer queries.

Free observable analyzer for ip, domain and url: checks the value (a URL is reduced to its host) against the NetAPI compromised feed with one keyless request. Listed now sets a malicious evaluation, a listing of a parent domain or a past listing only a suspicious one, not listed creates no data model. Added to FREE_TO_USE_ANALYZERS.
@mlodic

mlodic commented Nov 16, 2026

Copy link
Copy Markdown
Member

please update the migration number (there are new changes in develop)

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants