timb-machine / timb-machine/linux-malware
[Intel]: https://www.cyberark.com/resources/threat-research-blog/kinsing-the-malware-with-two-faces
Open
Nobody has claimed this yet.
missing:tag:T1005
missing:tag:T1027.002
missing:tag:T1048
missing:tag:T1053.007
missing:tag:T1057
missing:tag:T1070.003
missing:tag:T1070.004
missing:tag:T1070.006
missing:tag:T1071.001
missing:tag:T1083
missing:tag:T1222
missing:tag:T1491
missing:tag:T1546.004
missing:tag:T1548.001
missing:tag:T1552.003
missing:tag:T1560
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
Impact
Finding
https://www.cyberark.com/resources/threat-research-blog/kinsing-the-malware-with-two-faces
Industry reference
No response
Malware reference
KinSing
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 CyberArk threat report and the issue's Malware reports fields, especially the KinSing reference and Impact parent threat. Done means the report is represented in the repository with its source and malware name; no target file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100