Create event-type/v2 Stealer Log Entry

docs/event-types/v2/blog-post.mdx

@@ -0,0 +1,26 @@
+---
+title: "Blog Post"
+---
+
+The `blog_post` type represents blog-style documents and text-based publications that have been discovered and indexed by Flare across document-sharing or content-hosting platforms such as Scribd, Medium, or public paste/document repositories.
+These records generally include technical manuals, guides, or articles that are accessible to the public, potentially containing sensitive, proprietary, or copyrighted materials.
+
+```json Example Content
+{
+  "event_type": "blog_post",
+  "metadata": {
+    "estimated_created_at": "2025-01-01T00:00:00Z",
+    "matched_at": "2025-01-01T00:00:00Z",
+    "severity": "info",
+    "uid": "blog_post/blog_name/123456789",
+    "flare_url": "https://app.flare.io/#/blog_post/blog_name/123456789"
+  },
+  "data": {
+    "url": "https://www.blog_name.com/document/123456789/post_slug",
+    "content": "Post content",
+    "description": "Post description",
+    "posted_at": "2025-01-01T00:00:00Z"
+  }
+}
+
+```

docs/event-types/v2/stealer-log.mdx

@@ -0,0 +1,64 @@
+---
+title: "Stealer Log"
+---
+
+The `stealer_log` (also observed as `bot` in some indices) represents a record of a compromised device whose credentials and browsing data were harvested by an information stealer malware (such as RedLine, Raccoon, or Vidar).
+These entries originate from dark-web marketplaces (for example, “Russian Market”) where attackers sell logs containing cookies, saved passwords, and session tokens from infected machines.
+Each document corresponds to a single device or “bot,” with metadata describing where and when it was first seen, its environment (OS, IP, ISP), and the websites and services discovered in its data.
+
+```json Example Content
+{
+  "data": {
+    "name": null,
+    "installed_at": "2025-01-01T00:00:00.000000+00:00",
+    "updated_at": null,
+    "isp": null,
+    "information": null,
+    "victim_information": {
+      "ip_address": "127.0.0.1",
+      "ip_network": null,
+      "username": "admin",
+      "country_code": "USA",
+      "zip_code": "",
+      "location": "",
+      "hwid": "",
+      "current_language": "",
+      "screensize_width": 1920,
+      "screensize_height": 1080,
+      "timezone": "UTC+7",
+      "os": "Windows 10 22H2 Pro (Build 19045) (64 Bit)",
+      "uac": "",
+      "process_elevation": null,
+      "available_keyboards": [
+        "English"
+      ],
+      "hardware": [
+        "CPU: Intel(R) Core(TM) i3-10105F CPU @ 3.70GHz (4 cores, 8 threads)",
+        "RAM: 31.92 GB",
+        "HOSTNAME: DESKTOP-123456"
+      ],
+      "anti_viruses": null
+    },
+    "malware_information": {
+      "malware_family": "Lumastealer",
+      "build_id": "",
+      "file_location": "",
+      "infected_at": "2025-01-01T00:00:00.000000+00:00"
+    }
+  },
+  "event_type": "stealer_log",
+  "metadata": {
+    "estimated_created_at": "2025-01-01T00:00:00.000000+00:00",
+    "matched_at": "2025-01-01T00:00:00.000000+00:00",
+    "severity": "critical",
+    "uid": "stealer_log/stealer_logs/123456789",
+    "flare_url": "https://app.example.com/#/stealer_log/stealer_logs/123456789"
+  },
+}
+```
+
+{/*
+  TODO: Figure out whether we want an explanation of some/all of the return fields
+This could then be used by the documentation page for the new event endpoint rather than replace
+the existing event-types?
+*/}