timb-machine / timb-machine/linux-malware
[Intel]: https://cybersecurity.att.com/blogs/labs-research/prism-attacks-fly-under-the-radar
Open
Nobody has claimed this yet.
missing:tactics
missing:tag:Non-persistentStorage
missing:tag:ProcessTreeSpoofing
missing:tag:RedirectionToNull
missing:tag:T1005
missing:tag:T1021.002
missing:tag:T1048
missing:tag:T1057
missing:tag:T1070.003
missing:tag:T1070.004
missing:tag:T1071.001
missing:tag:T1071.004
missing:tag:T1215
missing:tag:T1491
missing:tag:T1546.004
missing:tag:T1552.003
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://cybersecurity.att.com/blogs/labs-research/prism-attacks-fly-under-the-radar
Industry reference
PRISM
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 PRISM report first and inspect existing entries in the linux-malware repository to determine how malware reports are recorded. Done means adding this finding in the repository's established format, but the issue does not name a target file or test.
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