timb-machine / timb-machine/linux-malware
[Intel]: https://github.com/timb-machine/obscure-forensics
Open
Nobody has claimed this yet.
missing:tactics
missing:tag:Non-persistentStorage
missing:tag:T1003.008
missing:tag:T1005
missing:tag:T1027.002
missing:tag:T1048
missing:tag:T1057
missing:tag:T1069
missing:tag:T1070.002
missing:tag:T1070.004
missing:tag:T1071.001
missing:tag:T1078.003
missing:tag:T1083
missing:tag:T1491
missing:tag:T1560
missing:tag:T1567
missing:tag:T1573
missing:tag:T1590
missing:tag:T1602.001
new
- Dominant language
- HTML
- Stars
- 1.2k
- Forks
- 95
- PR merge metrics
- No merged PRs in 30d
Description
Area
Defensive techniques
Parent threat
No response
Finding
https://github.com/timb-machine/obscure-forensics
Industry reference
No response
Malware reference
No response
Actor reference
No response
Component
No response
Scenario
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked obscure-forensics project and inspect existing entries in linux-malware to find where defensive-technique findings are recorded. Add the finding using the repository's established format, including any relevant details that can be verified from the linked source, and confirm the entry matches surrounding content.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100