timb-machine / timb-machine/linux-malware

[Intel]: https://www.gosecure.net/blog/2018/02/14/chaos-a-stolen-backdoor-rising/

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

Nobody has claimed this yet.

missing:tactics missing:tag:T1005 missing:tag:T1027.002 missing:tag:T1037 missing:tag:T1046 missing:tag:T1048 missing:tag:T1053.003 missing:tag:T1057 missing:tag:T1070.003 missing:tag:T1070.004 missing:tag:T1071.001 missing:tag:T1083 missing:tag:T1491 missing:tag:T1546.004 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

No response

Finding

https://www.gosecure.net/blog/2018/02/14/chaos-a-stolen-backdoor-rising/

Industry reference

uses:Go

Malware reference

Chaos (sebd)
/malware/binaries/Chaos

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 GoSecure article and inspecting the existing malware/binaries/Chaos entry. Compare this report with nearby malware entries to determine the expected representation and documentation; completion should add the Chaos reference consistently, but the issue does not specify the exact change.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
security
Issue type
Feature
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.