@blamejs/exceptd-skills 0.12.25 → 0.12.26

package/data/_indexes/section-offsets.json

@@ -3165,6 +3165,100 @@
         }
       ]
     },
+    "sector-telecom": {
+      "path": "skills/sector-telecom/skill.md",
+      "total_bytes": 20782,
+      "total_lines": 260,
+      "frontmatter": {
+        "line_start": 1,
+        "line_end": 74,
+        "byte_start": 0,
+        "byte_end": 1909
+      },
+      "sections": [
+        {
+          "name": "Threat Context (mid-2026)",
+          "normalized_name": "threat-context",
+          "line": 76,
+          "byte_start": 1910,
+          "byte_end": 5098,
+          "bytes": 3188,
+          "h3_count": 0
+        },
+        {
+          "name": "Framework Lag Declaration",
+          "normalized_name": "framework-lag-declaration",
+          "line": 90,
+          "byte_start": 5098,
+          "byte_end": 7180,
+          "bytes": 2082,
+          "h3_count": 0
+        },
+        {
+          "name": "TTP Mapping",
+          "normalized_name": "ttp-mapping",
+          "line": 94,
+          "byte_start": 7180,
+          "byte_end": 8614,
+          "bytes": 1434,
+          "h3_count": 0
+        },
+        {
+          "name": "Exploit Availability Matrix",
+          "normalized_name": "exploit-availability-matrix",
+          "line": 108,
+          "byte_start": 8614,
+          "byte_end": 9808,
+          "bytes": 1194,
+          "h3_count": 0
+        },
+        {
+          "name": "Analysis Procedure",
+          "normalized_name": "analysis-procedure",
+          "line": 121,
+          "byte_start": 9808,
+          "byte_end": 15637,
+          "bytes": 5829,
+          "h3_count": 7
+        },
+        {
+          "name": "Output Format",
+          "normalized_name": "output-format",
+          "line": 183,
+          "byte_start": 15637,
+          "byte_end": 17152,
+          "bytes": 1515,
+          "h3_count": 0
+        },
+        {
+          "name": "Compliance Theater Check",
+          "normalized_name": "compliance-theater-check",
+          "line": 231,
+          "byte_start": 17152,
+          "byte_end": 19359,
+          "bytes": 2207,
+          "h3_count": 0
+        },
+        {
+          "name": "Defensive Countermeasure Mapping",
+          "normalized_name": "defensive-countermeasure-mapping",
+          "line": 243,
+          "byte_start": 19359,
+          "byte_end": 20110,
+          "bytes": 751,
+          "h3_count": 0
+        },
+        {
+          "name": "Hand-Off / Related Skills",
+          "normalized_name": "hand-off",
+          "line": 253,
+          "byte_start": 20110,
+          "byte_end": 20782,
+          "bytes": 672,
+          "h3_count": 0
+        }
+      ]
+    },
     "api-security": {
       "path": "skills/api-security/skill.md",
       "total_bytes": 35524,

package/data/_indexes/stale-content.json

@@ -3,19 +3,31 @@
     "schema_version": "1.0.0",
     "reference_date": "2026-05-01",
     "note": "Stale-content snapshot derived from audit-cross-skill checks. Re-runs of build-indexes against the same inputs produce byte-identical output (reference_date is manifest.threat_review_date, not 'now'). audit-cross-skill.js remains the canonical interactive audit.",
-    "finding_count": 1,
+    "finding_count": 3,
     "by_severity": {
       "high": 0,
-      "medium": 1,
+      "medium": 3,
       "low": 0
     }
   },
   "findings": [
+    {
+      "severity": "medium",
+      "category": "badge_drift",
+      "artifact": "README.md",
+      "detail": "skills badge shows 38, manifest has 39"
+    },
     {
       "severity": "medium",
       "category": "badge_drift",
       "artifact": "README.md",
       "detail": "jurisdictions badge shows 35, live count is 34"
+    },
+    {
+      "severity": "medium",
+      "category": "researcher_claim_drift",
+      "artifact": "skills/researcher/skill.md",
+      "detail": "claims 37 specialized skills downstream; live count is 38"
     }
   ]
 }

package/data/_indexes/summary-cards.json

@@ -1351,6 +1351,60 @@
         "supply-chain-integrity"
       ]
     },
+    "sector-telecom": {
+      "description": "Telecom and 5G security for mid-2026 — Salt Typhoon, Volt Typhoon, CALEA / IPA-LI gateway compromise, signaling-protocol abuse (SS7 / Diameter / GTP), 5G N6 / N9 isolation, gNB / DU / CU integrity, OEM-equipment supply-chain compromise, AI-RAN / O-RAN security",
+      "threat_context_excerpt": "**Salt Typhoon (China nation-state; PRC Ministry of State Security nexus).** The 2024–2026 campaign — disclosed in successive Five Eyes joint advisories from October 2024 onward (CISA / NSA / FBI joint product reissued through 2025–2026) — compromised at least nine US carriers (publicly named: AT&T, Verizon, T-Mobile US, Lumen, Charter, Cox, Windstream, Consolidated, plus undisclosed others) and extended to AU / CA / NZ / UK Tier-1 carriers. Threat actor TTPs map to T1199 (Trusted Relationship) via OEM vendor supply chain, T1098 (Account Manipulation) for persistent admin access on NMS, and ...",
+      "produces": "The investigation evidence bundle returned by phase 5 + 6 has this shape:\n\n```json\n{\n  \"session_id\": \"telecom-<iso>\",\n  \"playbook_id\": \"sector-telecom\",\n  \"classification\": \"detected | clean | not_detected | inconclusive\",\n  \"evidence_hash\": \"sha256:...\",\n  \"telecom_specific_findings\": {\n    \"li_gateway_audit\": {\n      \"anomalous_activations\": 0,\n      \"activations_outside_ticket\": 0,\n      \"outbound_tunnel_to_non_allowlist_ip\": 0\n    },\n    \"gnb_attestation_state\": {\n      \"expected_hashes_compared\": 0,\n      \"drifted_basestations\": [],\n      \"downgrade_events\": 0\n    },\n    \"signaling_anomal ...",
+      "key_xrefs": {
+        "cwe_refs": [
+          "CWE-287",
+          "CWE-306",
+          "CWE-918"
+        ],
+        "d3fend_refs": [
+          "D3-NTA",
+          "D3-NTPM",
+          "D3-IOPR",
+          "D3-NI"
+        ],
+        "framework_gaps": [
+          "FCC-CPNI-4.1",
+          "FCC-Cyber-Incident-Notification-2024",
+          "NIS2-Annex-I-Telecom",
+          "DORA-Art-21-Telecom-ICT",
+          "UK-CAF-B5",
+          "AU-ISM-1556",
+          "GSMA-NESAS-Deployment",
+          "3GPP-TR-33.926",
+          "ITU-T-X.805"
+        ],
+        "atlas_refs": [
+          "AML.T0040"
+        ],
+        "attack_refs": [
+          "T1071",
+          "T1078",
+          "T1098",
+          "T1190",
+          "T1199",
+          "T1556"
+        ],
+        "rfc_refs": [
+          "RFC-9622"
+        ],
+        "dlp_refs": []
+      },
+      "trigger_count": 22,
+      "atlas_count": 1,
+      "attack_count": 6,
+      "framework_gap_count": 9,
+      "cwe_count": 3,
+      "d3fend_count": 4,
+      "rfc_count": 1,
+      "last_threat_review": "2026-05-15",
+      "path": "skills/sector-telecom/skill.md",
+      "handoff_targets": []
+    },
     "api-security": {
       "description": "API security for mid-2026 — OWASP API Top 10 2023, AI-API specific (rate limits, prompt-shape egress, MCP HTTP transport), GraphQL + gRPC + REST + WebSocket attack surfaces, API gateway posture, BOLA/BFLA/SSRF/Mass Assignment",
       "threat_context_excerpt": "APIs are now the integration substrate of every non-trivial system. The mid-2026 enterprise app is a thin shell of UI calling a fan-out of REST, GraphQL, gRPC, and WebSocket APIs — many of which themselves call **AI-API services** (OpenAI, Anthropic, Google Gemini, AWS Bedrock, Azure OpenAI) on the user's behalf. Legacy web-application firewalls were built for HTML form posts and inspect REST badly, GraphQL barely, gRPC binary framing not at all, and AI-API egress not at all. The defensive perimeter has moved from the WAF to the **API gateway and the egress policy**.",

package/data/_indexes/token-budget.json

@@ -3,9 +3,9 @@
     "schema_version": "1.0.0",
     "tokenizer_note": "Character-density approximation: 1 token ≈ 4 chars. This is the canonical rule-of-thumb for OpenAI tokenizers on English+technical text. Claude's tokenizer is typically more efficient on prose; treat this as an upper-bound budget for both. Consumers with stricter precision needs should re-tokenize with their own tokenizer.",
     "approx_chars_per_token": 4,
-    "total_chars": 1430239,
-    "total_approx_tokens": 357564,
-    "skill_count": 38
+    "total_chars": 1450921,
+    "total_approx_tokens": 362735,
+    "skill_count": 39
   },
   "skills": {
     "kernel-lpe-triage": {
@@ -1843,6 +1843,61 @@
         }
       }
     },
+    "sector-telecom": {
+      "path": "skills/sector-telecom/skill.md",
+      "bytes": 20782,
+      "chars": 20682,
+      "lines": 260,
+      "approx_tokens": 5171,
+      "approx_chars_per_token": 4,
+      "sections": {
+        "threat-context": {
+          "bytes": 3188,
+          "chars": 3174,
+          "approx_tokens": 794
+        },
+        "framework-lag-declaration": {
+          "bytes": 2082,
+          "chars": 2080,
+          "approx_tokens": 520
+        },
+        "ttp-mapping": {
+          "bytes": 1434,
+          "chars": 1422,
+          "approx_tokens": 356
+        },
+        "exploit-availability-matrix": {
+          "bytes": 1194,
+          "chars": 1194,
+          "approx_tokens": 299
+        },
+        "analysis-procedure": {
+          "bytes": 5829,
+          "chars": 5773,
+          "approx_tokens": 1443
+        },
+        "output-format": {
+          "bytes": 1515,
+          "chars": 1515,
+          "approx_tokens": 379
+        },
+        "compliance-theater-check": {
+          "bytes": 2207,
+          "chars": 2203,
+          "approx_tokens": 551
+        },
+        "defensive-countermeasure-mapping": {
+          "bytes": 751,
+          "chars": 751,
+          "approx_tokens": 188
+        },
+        "hand-off": {
+          "bytes": 672,
+          "chars": 662,
+          "approx_tokens": 166
+        }
+      }
+    },
     "api-security": {
       "path": "skills/api-security/skill.md",
       "bytes": 35524,

package/data/_indexes/trigger-table.json

@@ -1046,6 +1046,72 @@
   "smart meter security": [
     "sector-energy"
   ],
+  "telecom security": [
+    "sector-telecom"
+  ],
+  "5g core": [
+    "sector-telecom"
+  ],
+  "salt typhoon": [
+    "sector-telecom"
+  ],
+  "volt typhoon": [
+    "sector-telecom"
+  ],
+  "gnb integrity": [
+    "sector-telecom"
+  ],
+  "lawful intercept": [
+    "sector-telecom"
+  ],
+  "calea": [
+    "sector-telecom"
+  ],
+  "fcc cpni": [
+    "sector-telecom"
+  ],
+  "4-business-day notification": [
+    "sector-telecom"
+  ],
+  "gsma nesas": [
+    "sector-telecom"
+  ],
+  "ss7": [
+    "sector-telecom"
+  ],
+  "diameter": [
+    "sector-telecom"
+  ],
+  "gtp": [
+    "sector-telecom"
+  ],
+  "3gpp ts 33.501": [
+    "sector-telecom"
+  ],
+  "3gpp tr 33.926": [
+    "sector-telecom"
+  ],
+  "o-ran": [
+    "sector-telecom"
+  ],
+  "n6 n9 isolation": [
+    "sector-telecom"
+  ],
+  "nis2 annex i": [
+    "sector-telecom"
+  ],
+  "uk tsa 2021": [
+    "sector-telecom"
+  ],
+  "au soci": [
+    "sector-telecom"
+  ],
+  "tssr": [
+    "sector-telecom"
+  ],
+  "itu-t x.805": [
+    "sector-telecom"
+  ],
   "api security": [
     "api-security"
   ],

package/data/_indexes/xref.json

@@ -72,6 +72,7 @@
       "api-security",
       "attack-surface-pentest",
       "mcp-agent-trust",
+      "sector-telecom",
       "webapp-security"
     ],
     "CWE-1395": [
@@ -154,12 +155,14 @@
       "sector-energy",
       "sector-financial",
       "sector-healthcare",
+      "sector-telecom",
       "webapp-security"
     ],
     "CWE-306": [
       "identity-assurance",
       "ot-ics-security",
-      "sector-energy"
+      "sector-energy",
+      "sector-telecom"
     ],
     "CWE-798": [
       "cloud-security",
@@ -217,7 +220,8 @@
       "defensive-countermeasure-mapping",
       "dlp-gap-analysis",
       "fuzz-testing-strategy",
-      "rag-pipeline-security"
+      "rag-pipeline-security",
+      "sector-telecom"
     ],
     "D3-NTA": [
       "ai-attack-surface",
@@ -225,7 +229,8 @@
       "attack-surface-pentest",
       "defensive-countermeasure-mapping",
       "dlp-gap-analysis",
-      "rag-pipeline-security"
+      "rag-pipeline-security",
+      "sector-telecom"
     ],
     "D3-CBAN": [
       "defensive-countermeasure-mapping",
@@ -259,12 +264,14 @@
     ],
     "D3-NI": [
       "ai-c2-detection",
-      "defensive-countermeasure-mapping"
+      "defensive-countermeasure-mapping",
+      "sector-telecom"
     ],
     "D3-NTPM": [
       "ai-c2-detection",
       "defensive-countermeasure-mapping",
-      "dlp-gap-analysis"
+      "dlp-gap-analysis",
+      "sector-telecom"
     ],
     "D3-FE": [
       "defensive-countermeasure-mapping",
@@ -511,6 +518,33 @@
     "NERC-CIP-007-6-R4": [
       "ot-ics-security",
       "sector-energy"
+    ],
+    "FCC-CPNI-4.1": [
+      "sector-telecom"
+    ],
+    "FCC-Cyber-Incident-Notification-2024": [
+      "sector-telecom"
+    ],
+    "NIS2-Annex-I-Telecom": [
+      "sector-telecom"
+    ],
+    "DORA-Art-21-Telecom-ICT": [
+      "sector-telecom"
+    ],
+    "UK-CAF-B5": [
+      "sector-telecom"
+    ],
+    "AU-ISM-1556": [
+      "sector-telecom"
+    ],
+    "GSMA-NESAS-Deployment": [
+      "sector-telecom"
+    ],
+    "3GPP-TR-33.926": [
+      "sector-telecom"
+    ],
+    "ITU-T-X.805": [
+      "sector-telecom"
     ]
   },
   "atlas_refs": {
@@ -580,6 +614,9 @@
       "mlops-security",
       "ot-ics-security",
       "supply-chain-integrity"
+    ],
+    "AML.T0040": [
+      "sector-telecom"
     ]
   },
   "attack_refs": {
@@ -613,6 +650,7 @@
       "sector-energy",
       "sector-federal-government",
       "sector-financial",
+      "sector-telecom",
       "webapp-security"
     ],
     "T1195.001": [
@@ -626,7 +664,8 @@
       "rag-pipeline-security"
     ],
     "T1071": [
-      "ai-c2-detection"
+      "ai-c2-detection",
+      "sector-telecom"
     ],
     "T1102": [
       "ai-c2-detection"
@@ -647,7 +686,8 @@
       "incident-response-playbook",
       "sector-energy",
       "sector-financial",
-      "sector-healthcare"
+      "sector-healthcare",
+      "sector-telecom"
     ],
     "T1567": [
       "age-gates-child-safety",
@@ -677,7 +717,8 @@
       "supply-chain-integrity"
     ],
     "T1556": [
-      "identity-assurance"
+      "identity-assurance",
+      "sector-telecom"
     ],
     "T1110": [
       "identity-assurance"
@@ -697,6 +738,12 @@
       "incident-response-playbook",
       "sector-financial"
     ],
+    "T1098": [
+      "sector-telecom"
+    ],
+    "T1199": [
+      "sector-telecom"
+    ],
     "T1552": [
       "cloud-security"
     ],
@@ -812,6 +859,9 @@
     ],
     "RFC-9106": [
       "pqc-first"
+    ],
+    "RFC-9622": [
+      "sector-telecom"
     ]
   },
   "dlp_refs": {}

package/data/atlas-ttps.json

@@ -53,6 +53,43 @@
     ],
     "last_verified": "2026-05-15"
   },
+  "AML.T0040": {
+    "id": "AML.T0040",
+    "name": "Tool / Plugin Compromise",
+    "tactic": "Execution",
+    "description": "Adversary compromises an LLM tool-call surface or agent plugin layer — for example an MCP server, a tool registered with an OpenAI Codex / Anthropic Claude Code session, or a Copilot / Cursor agent plugin — to gain code execution within the agent runtime. The compromised tool exposes operator-controlled inputs (filesystem paths, shell commands, API endpoints) that the LLM invokes on behalf of the operator, bypassing the operator-side trust boundary.",
+    "subtechniques": [
+      "AML.T0040.000 — MCP server typosquat / registry compromise",
+      "AML.T0040.001 — Agent plugin authorization bypass via prompt-injection-induced consent",
+      "AML.T0040.002 — Stdio-transport command injection (Anthropic MCP SDK class)"
+    ],
+    "real_world_instances": [
+      "CVE-2026-30623 (Anthropic MCP SDK stdio command-injection class — 30+ MCP servers affected)",
+      "Pwn2Own Berlin 2026 — Viettel Cyber Security Claude Code collision (MCP-class bug)",
+      "Pwn2Own Berlin 2026 — STARLabs SG five-bug LM Studio chain",
+      "Pwn2Own Berlin 2026 — Compass Security OpenAI Codex CWE-150 chain"
+    ],
+    "framework_gap": true,
+    "framework_gap_detail": "No framework currently models the agent-runtime tool-call trust boundary. NIST 800-53 CM-7 (Least Functionality) was designed for OS-level execution allowlisting, not for AI-agent tool registries. ISO 27001:2022 A.5.20 (Information security in supplier relationships) does not reach plugin-level supplier identity in the agent runtime. The MCP-server-registry surface is closest analogue to a package registry; supply-chain controls (SLSA, sigstore) are not yet applied to MCP registries operationally.",
+    "controls_that_partially_help": [
+      "NIST-800-53-CM-7",
+      "NIST-800-53-AC-3",
+      "ISO-27001-2022-A.8.30"
+    ],
+    "controls_that_dont_help": [
+      "Traditional WAF / API gateway controls — agent-side calls bypass these by design",
+      "OS-level antimalware — the agent runtime invokes the tool inside its own process trust boundary"
+    ],
+    "detection": "MCP-server inventory + signature attestation; tool-call audit logs reviewed for typosquat patterns; agent-side outbound API call monitoring for credential exfiltration patterns; plugin-installation event correlation with prompt-injection IOCs.",
+    "exceptd_skills": [
+      "mcp-agent-trust",
+      "ai-attack-surface",
+      "mcp-supply-chain"
+    ],
+    "secure_ai_v2_layer": true,
+    "maturity": "high",
+    "last_verified": "2026-05-15"
+  },
   "AML.T0010": {
     "id": "AML.T0010",
     "name": "ML Supply Chain Compromise",