Talk:Infostealer
![]() | Infostealer is currently a Computing and engineering good article nominee. Nominated by Sohom (talk) at 14:42, 17 August 2024 (UTC) Anyone who has not contributed significantly to (or nominated) this article may review it according to the good article criteria to decide whether or not to list it as a good article. To start the review process, click start review and save the page. (See here for the good article instructions.) Short description: Malicious software used to steal information |
![]() | This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||
|
Readability review
[edit]Howdy! Just going to leave some suggestions for improvement, as I offered to do on discord :) this is only for the lead and first section, as i got tired and would rather post something than nothing.
- First paragraph: "session cookies" isn't widely understood and "threat actor" is jargon
Infostealers usually consist of two parts: the bot framework that allows the attacker to configure the behaviour of the infostealer on the victim's computer, and a management panel that takes the form of a server to which the infostealer sends data.
Not sure these are great definitions for "bot framework" and "management panel"Infostealers are usually distributed under the malware-as-a-service (MaaS) model, where developers allow other parties to use their infostealers for subscription fees.
Might want to make the distinction between the use and distribution of infostealers a bit more clear, since they both involve "sending" infostealer somewhere- Overview question: what differentiates infostealers from malware in general?
- Does the management interface function as a web server, or operate on the same web server the infostealer sends information back to?
Hope this helps :) theleekycauldron (talk • she/her) 05:43, 4 September 2024 (UTC)