timb-machine / timb-machine/linux-malware
[Intel]: https://elastic.github.io/security-research/intelligence/2022/03/03.dirty-pipe/article/
Open
Nobody has claimed this yet.
missing:tactics
missing:tag:T1003.008
missing:tag:T1005
missing:tag:T1007
missing:tag:T1037
missing:tag:T1048
missing:tag:T1053.006
missing:tag:T1057
missing:tag:T1070.002
missing:tag:T1070.004
missing:tag:T1071.001
missing:tag:T1078.003
missing:tag:T1083
missing:tag:T1491
missing:tag:T1543.002
missing:tag:T1548.003
missing:tag:T1567
missing:tag:T1573
missing:tag:T1590
new
- Dominant language
- HTML
- Stars
- 1.2k
- Forks
- 95
- PR merge metrics
- No merged PRs in 30d
Description
Area
Defensive tools
Parent threat
No response
Finding
https://elastic.github.io/security-research/intelligence/2022/03/03.dirty-pipe/article/
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
Read the linked Dirty Pipe research article first, then inspect existing entries in the repository to determine how defensive-tool intelligence is recorded. No file, test, or entry point is named, so confirm the expected format and scope with the project before starting; done means the finding is represented consistently with comparable entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100