Compromised
D3v0o0Nu119/2/20261 min read
#soc/dfir#htb#easy
Compromised
Platform: HackTheBox | Type: SOC/DFIR | Difficulty: Easy | Author: D3v0o0Nu11 | Date: 2026-02-10
Scenario
Our SOC team detected suspicious activity in Network Traffic, the machine has been compromised and company information that should not have been there has now been stolen – it’s up to you to figure out what has happened and what data has been taken.
Key Questions
- What indicators of compromise exist?
- What attack chain / MITRE techniques were used?
- What is the full timeline?
Investigation Timeline
| Time | Event | Evidence / Source |
|---|---|---|
| — | ASDA |
Evidence Analysed
- Tools: per the investigation narrative.
- Artifacts: per the investigation narrative.
Detailed Investigation
- ASDA
1ST QUESTION -> ANS:
REDACTED
3RD QUESTION -> ANS:
REDACTED
5TH QUESTION -> ANS:
REDACTED
7TH QUESTION -> ANS:
REDACTED
Findings
- Persistence mechanism — As documented in the investigation steps.
- Initial access — As documented in the investigation steps.
- Impact — As documented in the investigation steps.
MITRE ATT&CK Mapping
| Tactic | Technique | ID |
|---|---|---|
| — | — | — |
Answers / Flags
- 1ST QUESTION -> ANS:REDACTED
- 2ND QUESTION -> ANS:REDACTED
- 3RD QUESTION -> ANS:REDACTED
- 4TH QUESTION -> ANS:REDACTED
- 5TH QUESTION -> ANS:REDACTED
- 6TH QUESTION -> ANS:REDACTED
- 7TH QUESTION -> ANS:REDACTED
- 8TH QUESTION -> ANS:REDACTED
Lessons Learned
- Correlate artifacts across evidence sources to build a timeline.
- Map findings to MITRE ATT&CK techniques.
- Document IoCs for detection engineering.