timb-machine / timb-machine/linux-malware
[Intel]: https://old.reddit.com/r/LinuxMalware/comments/a66dsz/ddostf_still_lurking_arm_boxes/
Open
Nobody has claimed this yet.
missing:tactics
missing:tag:T1021.002
missing:tag:T1048
missing:tag:T1057
missing:tag:T1059.006
missing:tag:T1070.003
missing:tag:T1070.004
missing:tag:T1071.001
missing:tag:T1083
missing:tag:T1491
missing:tag:T1552.003
missing:tag:T1567
missing:tag:T1573
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://old.reddit.com/r/LinuxMalware/comments/a66dsz/ddostf_still_lurking_arm_boxes/
Industry reference
DDoSTF (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
Start with the Finding link and the issue's Malware reports template sections, especially the source and classification fields. Done would mean the DDoSTF report is recorded in the repository's tracking format with its relevant reference; no target file or test is named in the payload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100