timb-machine / timb-machine/linux-malware

[Intel]: https://cybersecurity.att.com/blogs/labs-research/botenago-strike-again-malware-source-code-uploaded-to-github

Open
#97 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

missing:tactics missing:tag:T1005 missing:tag:T1048 missing:tag:T1070.004 missing:tag:T1071.001 missing:tag:T1491 missing:tag:T1518 missing:tag:T1546.004 missing:tag:T1567 missing:tag:T1573 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/botenago-strike-again-malware-source-code-uploaded-to-github

Industry reference

Botenago

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked Botenago report and reviewing existing malware-report entries in the repository to determine how findings are recorded. Use the report as the source for a corresponding entry; done means the Botenago finding is documented consistently with the repository’s existing reports.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, security
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.