timb-machine / timb-machine/linux-malware

[Intel]: https://www.welivesecurity.com/2014/02/21/an-in-depth-analysis-of-linuxebury/

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

Nobody has claimed this yet.

missing:tactics missing:tag:RedirectionToNull missing:tag:T1003.008 missing:tag:T1021.004 missing:tag:T1027.002 missing:tag:T1048 missing:tag:T1057 missing:tag:T1070.004 missing:tag:T1071.001 missing:tag:T1078.003 missing:tag:T1083 missing:tag:T1491 missing:tag:T1518 missing:tag:T1546.004 missing:tag:T1556.003 missing:tag:T1567 missing:tag:T1573 missing:tag:T1574.006 missing:tag:T1590 new
Dominant language
HTML
Stars
1.2k
Forks
95
No merged PRs in 30d

Description

Area

Malware reports

Parent threat

No response

Finding

https://www.welivesecurity.com/2014/02/21/an-in-depth-analysis-of-linuxebury/

Industry reference

Ebury

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 reviewing the repository's existing malware reports and contribution guidance, then read the linked Ebury analysis. The issue names no target file or entry point; done would mean recording this source in the repository's established format with the Ebury reference.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.