timb-machine / timb-machine/linux-malware
[Intel]: https://www.sophos.com/en-us/medialibrary/PDFs/technical-papers/sophoslabs-cloud-snooper-report.pdf
Open
Nobody has claimed this yet.
missing:tactics
missing:tag:Non-persistentStorage
missing:tag:RedirectionToNull
missing:tag:T1005
missing:tag:T1021.001
missing:tag:T1046
missing:tag:T1048
missing:tag:T1057
missing:tag:T1070.003
missing:tag:T1070.004
missing:tag:T1083
missing:tag:T1215
missing:tag:T1546.004
missing:tag:T1548.003
missing:tag:T1552.003
missing:tag:T1562.004
missing:tag:T1573
missing:tag:T1574.007
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://www.sophos.com/en-us/medialibrary/PDFs/technical-papers/sophoslabs-cloud-snooper-report.pdf
Industry reference
Cloud Snooper
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
The issue names only the Cloud Snooper report and no repository file or test. Start by reading the linked Sophos report and comparing it with existing malware-report entries in the repository. Done means the report is recorded in the repository's established format with the available reference details.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100