mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-07-24 21:40:58 +03:00
- Add validated mitre_attack frontmatter to all 754 skills (286 distinct techniques), verified against MITRE ATT&CK v19.1 via the official mitreattack-python library: 0 revoked, deprecated, or invalid IDs - Curate precise per-skill technique IDs for forensics, malware-analysis, threat-intel, and red-team skills (e.g. DCSync -> T1003.006, Kerberoasting -> T1558.003, Pass-the-Ticket -> T1550.003) - Reconcile v19.1 tactic restructuring: Defense Evasion split into Stealth (TA0005) and Defense Impairment (TA0112); revoked T1562.* family and T1070.001/.002 remapped to active equivalents (T1685.*) - Normalize word-split tags across 35 skills (remove filename-derived stopword tags, add semantic cybersecurity tags) - Add api-reference.md for 3 skills that were missing it - Update README ATT&CK section with accurate v19.1 tactic distribution
113 lines
4.0 KiB
Markdown
113 lines
4.0 KiB
Markdown
---
|
|
name: analyzing-malicious-url-with-urlscan
|
|
description: URLScan.io is a free service for scanning and analyzing suspicious URLs.
|
|
It captures screenshots, DOM content, HTTP transactions, JavaScript behavior, and
|
|
network connections of web pages in an isolat
|
|
domain: cybersecurity
|
|
subdomain: phishing-defense
|
|
tags:
|
|
- phishing
|
|
- email-security
|
|
- social-engineering
|
|
- dmarc
|
|
- awareness
|
|
- url-analysis
|
|
- threat-intelligence
|
|
version: '1.0'
|
|
author: mahipal
|
|
license: Apache-2.0
|
|
atlas_techniques:
|
|
- AML.T0052
|
|
nist_csf:
|
|
- PR.AT-01
|
|
- DE.CM-09
|
|
- RS.CO-02
|
|
- DE.AE-02
|
|
mitre_attack:
|
|
- T1566.002
|
|
- T1204.001
|
|
- T1598.003
|
|
---
|
|
# Analyzing Malicious URL with URLScan
|
|
|
|
## Overview
|
|
URLScan.io is a free service for scanning and analyzing suspicious URLs. It captures screenshots, DOM content, HTTP transactions, JavaScript behavior, and network connections of web pages in an isolated environment. This skill covers using URLScan's web interface and API to investigate phishing URLs, credential harvesting pages, and malicious redirects without exposing the analyst's system to risk.
|
|
|
|
|
|
## When to Use
|
|
|
|
- When investigating security incidents that require analyzing malicious url with urlscan
|
|
- When building detection rules or threat hunting queries for this domain
|
|
- When SOC analysts need structured procedures for this analysis type
|
|
- When validating security monitoring coverage for related attack techniques
|
|
|
|
## Prerequisites
|
|
- URLScan.io account (free tier available, API key for automation)
|
|
- Python 3.8+ with requests library
|
|
- Understanding of HTTP protocols and web technologies
|
|
- Familiarity with phishing URL patterns
|
|
|
|
## Key Concepts
|
|
|
|
### URLScan Capabilities
|
|
1. **Safe browsing**: Renders URLs in isolated Chromium instance
|
|
2. **Screenshot capture**: Visual snapshot of the rendered page
|
|
3. **DOM analysis**: Full HTML content after JavaScript execution
|
|
4. **Network log**: All HTTP requests made by the page (HAR format)
|
|
5. **Certificate analysis**: SSL/TLS certificate details
|
|
6. **Technology detection**: Identifies web frameworks and libraries
|
|
7. **IP/ASN mapping**: Infrastructure intelligence
|
|
8. **Verdict**: Community and automated classification
|
|
|
|
### Phishing URL Red Flags
|
|
- Newly registered domains (< 30 days)
|
|
- Free hosting services (Wix, GitHub Pages, Firebase)
|
|
- URL shorteners hiding final destination
|
|
- Excessive subdomain depth (login.microsoft.com.evil.com)
|
|
- Brand name in subdomain or path, not domain
|
|
- Non-standard ports
|
|
- Data URIs or base64-encoded content
|
|
- JavaScript-heavy pages with minimal HTML
|
|
|
|
## Workflow
|
|
|
|
### Step 1: Submit URL to URLScan
|
|
```
|
|
Web: Navigate to https://urlscan.io and submit the suspicious URL
|
|
API: POST https://urlscan.io/api/v1/scan/
|
|
Header: API-Key: your-api-key
|
|
Body: {"url": "https://suspicious-url.com", "visibility": "private"}
|
|
```
|
|
|
|
### Step 2: Analyze Results
|
|
- Review screenshot for brand impersonation
|
|
- Check redirects and final destination URL
|
|
- Examine DOM for credential input forms
|
|
- Review network requests for data exfiltration endpoints
|
|
- Check SSL certificate validity and issuer
|
|
|
|
### Step 3: Extract IOCs
|
|
- Domains and IPs contacted
|
|
- URLs in redirect chain
|
|
- SHA-256 hashes of page resources
|
|
- JavaScript file hashes
|
|
|
|
### Step 4: Cross-Reference with Threat Intelligence
|
|
Use the `scripts/process.py` to automate URL scanning, extract IOCs, and cross-reference with VirusTotal, PhishTank, and Google Safe Browsing.
|
|
|
|
## Tools & Resources
|
|
- **URLScan.io**: https://urlscan.io/
|
|
- **URLScan API**: https://urlscan.io/docs/api/
|
|
- **VirusTotal URL Scanner**: https://www.virustotal.com/
|
|
- **PhishTank**: https://phishtank.org/
|
|
- **Google Safe Browsing**: https://transparencyreport.google.com/safe-browsing/search
|
|
- **Any.Run**: https://any.run/ (interactive sandbox)
|
|
- **Hybrid Analysis**: https://www.hybrid-analysis.com/
|
|
|
|
## Validation
|
|
- Successfully scan a suspicious URL via API
|
|
- Extract screenshot and identify brand impersonation
|
|
- Document complete redirect chain
|
|
- Generate IOC list from scan results
|
|
- Cross-reference findings with at least 2 threat intelligence sources
|