September 2026: Dark Web Credential Results, GitHub Monitoring, and Asset Hierarchy View

September product updates graphic with three illustrated cards for leaked credentials, GitHub monitoring, and asset hierarchy

Here is a roundup of the most relevant product updates from September. They focus on deeper threat visibility, new coverage, and faster ways to act on and integrate your data.

Redesigned dark web leaked credential results

If you use dark web monitoring, which is currently in beta, your leaked credential results now share a unified table layout across domain, email, and wallet searches. You can triage records by severity from Critical to Low, filter with summary tiles, and use bulk actions to acknowledge or reopen credentials. An upgraded record details drawer with keyboard navigation makes reviewing findings faster. You can also now search leaked credential records using cryptocurrency addresses and entities to identify compromised accounts tied to specific wallets.

To try it, open the dark web credentials search in your dashboard, or learn more about Dark Web Monitoring.

Dark web leaked credentials
One table for every search
DomainEmailWallet
12Critical
28High
41Medium
19Low
3 selectedAcknowledgeReopen
[email protected]CriticalStealer log
[email protected]CriticalBreach dump
[email protected]HighBreach dump
[email protected]MediumPaste site
SourceStealer log
Leak date2026-08-14
StatusOpen
Move between records with ↑↓

Search dark web credentials via the API

If you use dark web monitoring (currently in beta), you can now search leaked credentials and view affected targets programmatically through the public API. This lets you build leaked credential lookups directly into your own workflows and scripts rather than checking manually. Access is limited to organization owners, admins, and organization-scoped API keys.

See the Search Dark Web Credentials and List Dark Web Credential Targets docs.

Search dark web credentials
Public API
Request
POST/api/v2/dark-web/credentials/search
{
"slug": "acme",
"kind": "domain",
"target": "acme.com"
}
Response200 OK
{
"target": "acme.com",
"kind": "domain",
"total": 1,
"items": [
{
"email": "[email protected]",
"source": "Breach dump",
"leakDate": "2026-08-14"
}
]
}
Fields shortened for this example. Responses can include sensitive data, so use TLS and never log them.

GitHub monitoring for brand impersonation

GitHub monitoring is now available for brand impersonation across repositories, accounts, issues, pull requests, and code. It is on by default for some organizations and available to others on request, so contact your customer success representative to ask about access. This extends your coverage to a surface where fake projects and accounts often appear.

GitHub monitoring
New coverage
RepositoriesAccountsIssuesPull requestsCode
acme-login-helper
Possible impersonation
Uses your brand name and logo in the README
@acme-official-dev
Possible impersonation
Profile copies your brand name and avatar
Issue in acme-sdk-fork
Possible impersonation
Links to a fake login page
Update install script
Possible impersonation
Adds an unknown download link
install.sh
Possible impersonation
Contains a lookalike of your domain
Monitors repositories, accounts, issues, pull requests, and code for impersonation of your brand

Asset hierarchy view on Search

You can now open a Hierarchy tab on the Search page to explore an asset’s full domain and subdomain tree. The view shows parent, sibling, and child relationships alongside each asset’s block or allow status, so you can see how status is inherited across related assets. To try it, open the Hierarchy tab on the Search page.

Asset hierarchy
Search page
OverviewHierarchy
acme-support-login.comParentBlocked
login.acme-support-login.comSelectedBlocked: inherited
api.login.acme-support-login.comChildBlocked: inherited
pay.acme-support-login.comSiblingBlocked: inherited
help.acme-support-login.comSiblingAllowed

Smaller improvements

  • You can export detections to CSV from the Detections page (now called Suspected Threats). The export follows your active filters and search, and includes up to 10,000 rows.

  • Tumblr blogs and posts are now a dedicated asset type, with automated liveness checks and takedown tracking.

  • Webhooks have a new event, asset.escalation-resolved, that fires when an escalated threat is approved or rejected. The escalation event now also includes the reviewer’s comment and a direct link to the proposal. See the webhooks guide.

  • Report screenshots and image attachments can be previewed in a full-screen viewer in report details and in takedown evidence.

  • The Asset List API now returns all asset types in one paginated sweep when you leave out the type filter.

  • Glassdoor employer profiles are now supported as a dedicated asset type for monitoring and allowlisting.

  • Organization metrics and summary CSV exports now show the total count of submitted assets alongside total reports.

  • Asset details can now show an Enforcement Exhausted tag when all available takedown options have been pursued but the asset is still online because the provider has not acted.

  • The asset activity timeline now shows the threat’s earliest observed active date alongside ChainPatrol’s detection time.

  • Protected assets now appear at the top of your brand assets list.

Have questions about this month’s updates? Contact your customer success representative or email us.