timb-machine / timb-machine/linux-malware
[Intel]: https://blog.malwaremustdie.org/2016/08/mmd-0056-2016-linuxmirai-just.html
Open
Nobody has claimed this yet.
missing:tactics
missing:tag:ProcessTreeSpoofing
missing:tag:ProcessTreeSpoofingForking
missing:tag:RedirectionToNull
missing:tag:T1003.008
missing:tag:T1005
missing:tag:T1046
missing:tag:T1048
missing:tag:T1057
missing:tag:T1070.004
missing:tag:T1071.001
missing:tag:T1083
missing:tag:T1205
missing:tag:T1491
missing:tag:T1546.004
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
No response
Finding
https://blog.malwaremustdie.org/2016/08/mmd-0056-2016-linuxmirai-just.html
Industry reference
Mirai (by malwaremustdie.org)
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 MalwareMustDie report first, then inspect existing malware-report entries in the repository to determine the expected contribution format. The issue names no file or test; completion should consistently record the Mirai finding and allow its details to be checked against the linked report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100