# [CRIT] Stranger Danger: Live hack of how a Log4Shell exploit works

**Source:** Snyk
**Published:** 2022-01-25
**Article:** https://snyk.io/blog/stranger-danger-live-hack-log4shell-exploit/

## Threat Profile

Snyk Blog In this article
Written by Sarah Wills 
January 25, 2022
0 mins read The Log4Shell vulnerability took the Java community by surprise at the end of 2021, and many organizations are still mitigating its impact. To help development teams stay informed as the situation unfolds, Snyk has created and continues to update its Log4j vulnerability resource center .
During a recent Stranger Danger live hack , Simon Maple, Field CTO at Snyk, Eric Smalling, Senior Developer Advocate at Snyk, and Mi…

## Indicators of Compromise (high-fidelity only)

- **CVE:** `CVE-2021-44228`
- **Domain (defanged):** `evil.com`

## MITRE ATT&CK Techniques

- **T1190** — Exploit Public-Facing Application
- **T1071** — Application Layer Protocol

## Kill chain phases observed

_(none detected from narrative keywords)_

## Recommended hunts

### IOC-driven hunts (use shared templates)

These are standard IOC-substitution hunts — the canonical SPL and KQL live once in [`_TEMPLATES.md`](../_TEMPLATES.md), so we don't repeat the same boilerplate on every CVE / hash / network-IOC briefing.

- **Asset exposure — vulnerability matches article CVE(s)** ([template](../_TEMPLATES.md#asset-exposure)) — phase: **recon**, confidence: **High**
  - CVE(s): `CVE-2021-44228`

- **Network connections to article IPs / domains** ([template](../_TEMPLATES.md#network-ioc)) — phase: **c2**, confidence: **High**
  - IP / domain IOC(s): `evil.com`


## Why this matters

Severity classified as **CRIT** based on: CVE present, IOCs present, 2 use case(s) fired, 2 technique(s) inferred. Read the full article for actor attribution, tooling details, and any defanged IOCs in the body that aren't visible in the RSS summary.