Sibling comments covered the other stuff, but I'll clarify the particular "strange parallel universe" this article exists in: it's investigative web security / web-forensics journalism. And not the kind written by general-beat journalists, re-digested for a general "pop science" reader; but rather, the kind written by people who do such investigations themselves (whether they did the particular investigations they report on, or are getting the information from their trusted sources and contacts in the web-security community.)
A well-known web security journalist, who writes in this mode, is Brian Krebs of https://krebsonsecurity.com/.
This type of ingestigative web-security writing has three audiences:
- the "general" audience of non-security-focused IT professionals, who are nevertheless interested in security topics from afar;
- the "professional" audience of other web-security professionals, who do the exact same kinds of investigations the author themselves does (whether or not they then share their results publicly);
- and the "oppositional" audience, i.e. the very malicious-actor groups the investigations target.
Each article thus serves three purposes:
1. to the "general" audience, the article provides an entertaining and informative journalistic narrative (and this encourages this group to spread the article, to increase the likelihood people in the other two groups will read it);
2. to the "professional" audience, the article serves as an "investigation log" that must provide enough information to reproduce the derived information (so that the results can be trusted and acted upon), and/or so that the investigation can be taken further without wasting time doing things that have already been done (because each piece like this, if it doesn't end in the investigation target being cleaned up, serves double-duty as an invitation for collaboration, either directly, or via encouraging independent "federated investigations");
3. to the "oppositional" audience, the article acts as propaganda for the power and reach of the "side" of the investigators, with the intent of producing chilling effects against others doing the same thing; and, more specifically to would-be collaborators with the target group, acts to scare them off from doing that, cutting off the target group's resources.
Note the three-way conflict-of-interest this introduces: security professionals need to know how and where you got your information; general audiences don't really care and just find such info to be needless detail; and your investigation targets should ideally know as little as possible about these tools, so that they don't start enacting countermeasures to make these tools useless against them. (But it's good that the opposition is aware that these tools exist and understand the chain of inputs and outputs that goes through them -- to show exactly the sloppiness that got them got, and so prove that web security people are not just bluffing about having such powerful tools while actually parallel-reconstructing info they get via e.g. double-agents.)
This conflict-of-interest is mostly resolved by just naming these tools while describing them as little as possible, and absolutely never linking to them.
Security professionals are expected to recognize the names and know how to get access to them (if they don't have it already); general audiences are expected to just gloss over these names as some kind of technobabble (an expectation you and I, being curious-by-nature people, failed); and the opposition is expected to recognize that these tools exist, but either struggle to find them (these tools are often referred to by nicknames that are also names of larger services in other domains, so just punching the tool's name into google often does nothing), or struggle to get access to them. (With a specific additional goal of minimizing the knowledge the opposition has of these tools so that they can't socially-engineer their way into convincing some bureaucratic employer that they "should" be given access to them. Which means never describing how these tools work, providing screenshots of them, etc.)