timb-machine / timb-machine/linux-malware
[Intel]: http://www.foo.be/cours/dess-20042005/report/bigwar.html#sc
Open
Nobody has claimed this yet.
missing:tactics
missing:tag:Non-persistentStorage
missing:tag:T1003.008
missing:tag:T1005
missing:tag:T1021.004
missing:tag:T1027.002
missing:tag:T1057
missing:tag:T1069
missing:tag:T1070.004
missing:tag:T1070.006
missing:tag:T1071.001
missing:tag:T1071.002
missing:tag:T1078.003
missing:tag:T1222
missing:tag:T1491
missing:tag:T1546.004
missing:tag:T1548.001
missing:tag:T1567
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
http://www.foo.be/cours/dess-20042005/report/bigwar.html#sc
Industry reference
sc (similar code to luckscan)
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 BigWar report and compare its “sc” reference with the repository’s existing malware-report entries. The issue names no target file, test, or required change, so confirm the project’s entry format and intended scope before proceeding; done means the finding is recorded consistently with the project’s existing data.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, security
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100