Skip to content
Menu

VERISTADE / THREAT INVESTIGATION

Swarm Hunter.

Turn a warning into a clearer picture.

Swarm Hunter brings public reports and records your team is allowed to use into one review. Follow the sequence, see why a warning appeared and inspect the source before deciding what to check next.

For security reviewers and teams asking what happened and what needs a closer look.

Technical details & PDF

In development, with a local version for reviewing records. It is not ready for general production use. Connections to customer systems still need setup and testing. Availability and limits

WHAT YOU CAN INVESTIGATE

Three ways to start.

Start with a website or address mentioned in available reports, a reported lead or activity records you are allowed to inspect. Each path depends on the sources available for that review.

01 / A TARGET

Look into a website or address.

Start with a website, domain name or public IP address. Look for it in available reports and add records that help explain the activity.

You see what those sources contain. An address alone does not reveal private traffic or hidden agents.

02 / REPORTED LEADS

Find what deserves a closer look.

Look through reports of possible malware activity. Hunter puts the reports it rates as more important first and shows where each came from and when it was reported.

A report is a reason to look more closely. It doesn’t prove that an entire website or server is unsafe.

03 / INCOMING ACTIVITY

Review new warning signs.

A file you supply can provide new activity records. Review repeated actions and changes, then inspect the events supporting each warning.

A warning depends on what the records show and when they arrive. Missing or late records can change the finding.

EXAMPLE INVESTIGATION · FICTIONAL RECORDS

Repeated login failures.
Requests for sensitive records.

In this fictional example, a website records repeated failed logins followed by requests for private records. The sequence deserves review, but it has several possible explanations. Start by checking what the records show and what normal activity would look like.

1

Look at what changed.

In this example, the records show failed login attempts followed by requests for private information. Comparing them with normal activity helps a reviewer work out what changed.

Shown in this example: request times, attempted actions and recorded responses.

2

Connect the records.

Hunter groups related requests and puts them in order. Each warning points to the records behind it and shows what information is missing.

The connection comes from the available records, rather than a guessed link between addresses.

3

Review the case.

A person checks whether the activity was expected, what access the records show and whether to gather more information or respond.

Still unknown: who is behind the activity, whether AI is involved, and whether harm occurred.

Example only, using fictional records. Busy traffic, shared servers or repeated actions do not by themselves prove an attack.

EVIDENCE SOURCES

Know where
the evidence comes from.

A public report can identify a lead. Your team’s records can show activity in the systems they cover. These sources answer different questions, so Hunter keeps them separate for review.

Public malware reports

The local test version can collect reports from URLhaus, which lists reported malware links. Each report keeps its source, date and exact link.

These are reports about malware links, not proof of rogue AI agents. Hunter reads the reports without opening the reported malware links.

Records your team provides

A local file can supply new request records as they arrive: times, attempted actions and the service’s responses. Hunter can see only the activity included in that file.

Connecting a customer’s live system needs separate setup and testing. Entering a website address does not reveal its private traffic.

WHAT YOU LEARN

See the concern and the records behind it.

A useful warning should help a reviewer explain the concern from the original records and recognize what is missing. Check both before deciding what to do.

Why it needs attention

Review the related activity and the reasons a lead or warning was raised.

What supports the finding

Follow the source reports and records, with their times and known gaps.

What is still unknown

Consider normal explanations and missing records. A person decides what to do next. Hunter does not automatically block activity or change permissions.

CURRENT STATUS

An early version
for reviewing records.

The local review version has been checked with sample data for looking up targets, collecting reports and reviewing supplied activity records. These checks show behavior in those examples; they do not establish accuracy against real threats.

Before customer use

There is no online investigation service, activation or download here. Connections to live providers and customer systems still need to be checked for the proposed setup.

We have not established how reliably Hunter detects real threats or identifies coordinated AI agents. Work to connect it to Agent Defender is paused.

What the tests show

Earlier checks of version 0.4.0 used sample reports and fictional records. See the current status and Technical pages for later versions and their limits.

Check when a report was created, what it covers and what may be missing. A malware link does not make every page on the same server unsafe. New information can change a finding.

More investigation tools are being developed. They are not offered here as a released service.

LET’S TALK

What are you trying to understand?

Describe the concern, the kinds of records available and the decision you need to make. A general description is enough. Keep private records and passwords out of the contact form.

Swarm Hunter can be discussed on its own. Using it with other products would need separate setup and testing.

Plan a limited test
Technical details & PDF brief

For a deeper review, inspect supported record formats, source labels, storage and exports, tested versions and what remains unverified.