timb-machine / timb-machine/linux-malware

[Intel]: https://github.com/gaffe23/linux-inject

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

Nobody has claimed this yet.

missing:tactics missing:tag:ProcessTreeSpoofingForking missing:tag:T1055.008 missing:tag:T1057 missing:tag:T1070.004 missing:tag:T1548.003 missing:tag:T1574.006 missing:tag:T1622 new
Dominant language
HTML
Stars
1.2k
Forks
95
PR merge metrics
No merged PRs in 30d

Description

Area

Malware PoCs

Parent threat

No response

Finding

https://github.com/gaffe23/linux-inject

Industry reference

No response

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 linked linux-inject repository and the linux-malware repository's contribution conventions. Confirm whether the finding belongs in the Malware PoCs area and identify the repository's expected record format; done means the finding is documented consistently with the project's existing entries.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
security
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.