IoT Cameras and DVRs as DDoS Reflectors: Pros and Cons from Hacker’s Perspective
Bibliographic record
Abstract
The Mirai attacks of 2016 have shown the devastating DDoS potential of compromised IoT devices (primarily IoT cameras and DVRs), when nearly half a million of these devices were used to launch some of the largest and most devastating DDoS attacks recorded to date. One would hope that a full year later, the users and administrators of Internet-facing IoT devices have taken at least the basic measures towards reducing the likelihood that their devices get recruited as facilitators/executors of direct or reflected DDoS attacks. Unfortunately, the results of our recent study involving real-world IoT cameras and DVRs are rather discouraging as they show that: 1) with the existence of publicly accessible IoT search engines, such as Shodan, it has become easier than ever for hacker to discover and compromise IoT devices, of any kind and anywhere in the world, and 2) a significant number of these devices are inadequately protected against TCP-SYN floods and DDoS reflection - either by means of firewalls or at the OS-level. The aim of this article is to serve as a wake-up call to the users and administrators of Internet-facing IoT devices, and alert to the need to better protect these devices form being coopted by hackers for purposes of DDoS attacks.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.007 | 0.014 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.003 | 0.015 |
| Scholarly communication | 0.015 | 0.022 |
| Open science | 0.001 | 0.004 |
| Research integrity | 0.009 | 0.006 |
| Insufficient payload (model declined to judge) | 0.007 | 0.002 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".