timb-machine / timb-machine/linux-malware
[Intel]: https://darrenmartyn.ie/2021/11/29/analysis-of-the-lib__mdma-so-1-userland-rootkit/
Open
Nobody has claimed this yet.
missing:tag:T1005
missing:tag:T1021.002
missing:tag:T1027.002
missing:tag:T1048
missing:tag:T1057
missing:tag:T1070.003
missing:tag:T1070.004
missing:tag:T1071.001
missing:tag:T1083
missing:tag:T1491
missing:tag:T1548.003
missing:tag:T1552.003
missing:tag:T1560
missing:tag:T1567
missing:tag:T1573
missing:tag:T1574.006
missing:tag:T1590
new
- Dominant language
- HTML
- Stars
- 1.2k
- Forks
- 95
- PR merge metrics
- No merged PRs in 30d
Description
Area
Malware reports
Parent threat
Persistence, Defense Evasion
Finding
https://darrenmartyn.ie/2021/11/29/analysis-of-the-lib__mdma-so-1-userland-rootkit/
Industry reference
https://github.com/timb-machine/linux-malware/issues/530
Malware reference
lib__mdma
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
Start with the linked analysis of the lib__mdma userland rootkit and the referenced linux-malware issue. Review the repository's malware-report organization, then determine where this report belongs and verify that the lib__mdma finding is represented with its source link and threat context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- reverse-engineering, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100