timb-machine / timb-machine/linux-malware
[Intel]: https://blog.netlab.360.com/ghost-in-action-the-specter-botnet/
Open
Nobody has claimed this yet.
missing:tactics
missing:tag:Non-persistentStorage
missing:tag:T1027.002
missing:tag:T1048
missing:tag:T1057
missing:tag:T1070.004
missing:tag:T1071.001
missing:tag:T1222
missing:tag:T1491
missing:tag:T1546.004
missing:tag:T1548.001
missing:tag:T1560
missing:tag:T1562.004
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
Malware reports
Parent threat
No response
Finding
https://blog.netlab.360.com/ghost-in-action-the-specter-botnet/
Industry reference
No response
Malware reference
Specter
SideWalk
StageClient
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 Netlab report and the repository’s existing malware-report entries. Check how the report and the Specter, SideWalk, and StageClient references are represented, then confirm the relevant entry includes the supplied finding and malware names.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100