Forensia CTI Core

Summary

Ingested excerpt (first ~500 chars of normalized text).

How We Added WebAuthn to a Browser-Based RDP Client A look inside the reverse-engineering journey of building the first RDP client outside of Windows to support WebAuthn redirection. The post How We Added WebAuthn to a Browser-Based RDP Client appeared first on Unit 42 . How We Added WebAuthn to a Browser-Based RDP Client Menu Tools ATOMs Security Consulting About Us Under Attack? Threat Research Center Insights General General How We Added WebAuthn to a Browser-Based RDP C…

https://unit42.paloaltonetworks.com/webauthn-added-to-browser-based-rdp

sha256:59a0e48c15a326d2d207a8ef494ab2c3c81c0e5ee7180e70e6d49ab5e37e132f

What we pulled out

Deterministic extractor (IOC + allowlisted tokens + ATT&CK IDs present in DB).

cve1
md50
url1
ipv40
ipv60
sha10
domain8
sha2560
malware_token0
attack_pattern0
threat_actor_token0

Indicators

Linked with report → mentions → indicator. Values open the indicator workspace.

Type	Value	Link
domain	mstsc.exe	Open →
domain	okta.com	Open →
cve	CVE-2025-59287	Open →
domain	rdp.webauthn	Open →
domain	navigator.credentials	Open →
domain	navigator.credentials.create	Open →
domain

Malware families

Allowlist token matches only.

None extracted.

Threat actors mentioned

Allowlist mentions — not a formal attribution verdict.

None extracted.

ATT&CK techniques

MITRE IDs referenced in text and present in local technique table.

None linked (import ATT&CK or adjust text).

CONTINUE INVESTIGATION

High-signal pivots without leaving the thread you started in search.

All reports
Browse the report corpus.
Intel graph (first IOC)
Neighborhood from the first linked indicator.

← Back to reports