timb-machine / timb-machine/linux-malware

[Intel]: https://cujo.com/threat-alert-krane-malware/

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

Nobody has claimed this yet.

missing:tag:Non-persistentStorage missing:tag:T1005 missing:tag:T1021.002 missing:tag:T1027.002 missing:tag:T1048 missing:tag:T1053.003 missing:tag:T1057 missing:tag:T1070.003 missing:tag:T1070.004 missing:tag:T1070.006 missing:tag:T1071.001 missing:tag:T1083 missing:tag:T1222 missing:tag:T1491 missing:tag:T1546.004 missing:tag:T1548.001 missing:tag:T1552.003 missing:tag:T1560 missing:tag:T1567 missing:tag:T1573
Dominant language
HTML
Stars
1.2k
Forks
95
PR merge metrics
No merged PRs in 30d

Description

Area

Malware reports

Parent threat

Initial Access, Persistence, Defense Evasion, Impact

Finding

https://cujo.com/threat-alert-krane-malware/

Industry reference

attack:T1110.003:Password Spraying
attack:T098:Account Manipulation
attack:T1105:Ingress Tool Transfer
attack:T1562.003:Impair Command History Logging
attack:T1070.002:Clear Linux or Mac System Logs
attack:T1082:System Information Discovery
attack:T1018:Remote System Discovery
attack:T1021:Remote Services
uses:Non-persistentStorage

Malware reference

Krane
wltm

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 with the linked Cujo threat alert and compare its Krane and wltm details with existing malware reports in the repository. The payload names no target file or test; done means recording the report and its listed ATT&CK, storage, malware, and platform references in the repository’s established format.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
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.