From cb9542ecc23599e2006e36b7981ecb4abf68da92 Mon Sep 17 00:00:00 2001 From: RiccardoBiosas Date: Thu, 15 Oct 2026 15:26:22 +0700 Subject: [PATCH 1/2] ci(release): tag and publish a GitHub Release when a version bump reaches main No release had ever been tagged, so consumers could not pin a dataset version. The workflow reads package.json, skips if v already exists, extracts that version's CHANGELOG section as notes (failing if it is missing) and attaches the dist/ artifacts and the JSON Schema. CONTRIBUTING gains a Releasing section. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/release.yml | 66 +++++++++++++++++++++++++++++++++++ CONTRIBUTING.md | 9 +++++ 2 files changed, 75 insertions(+) create mode 100644 .github/workflows/release.yml diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml new file mode 100644 index 0000000..388d3f2 --- /dev/null +++ b/.github/workflows/release.yml @@ -0,0 +1,66 @@ +name: release + +# Tag and publish a GitHub Release whenever a dataset version bump reaches +# main. The version comes from package.json (kept in sync with CITATION.cff by +# `npm run validate`); the notes are that version's CHANGELOG section. Runs only +# when no v tag exists yet, so ordinary data merges are a no-op. +on: + push: + branches: [main] + paths: [package.json] + workflow_dispatch: + +permissions: + contents: write + +jobs: + release: + name: tag and publish + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v4 + with: + fetch-depth: 0 + - uses: actions/setup-node@v4 + with: + node-version: 20 + cache: npm + - run: npm ci + - run: npm test + + - name: Read version + id: version + run: echo "tag=v$(node -p "require('./package.json').version")" >> "$GITHUB_OUTPUT" + + - name: Skip if already tagged + id: exists + run: | + if git rev-parse -q --verify "refs/tags/${{ steps.version.outputs.tag }}" >/dev/null; then + echo "skip=true" >> "$GITHUB_OUTPUT" + fi + + - name: Extract release notes from CHANGELOG + if: steps.exists.outputs.skip != 'true' + run: | + v="${{ steps.version.outputs.tag }}"; v="${v#v}" + awk -v v="$v" ' + $0 ~ "^## \\[" v "\\]" { on = 1; next } + on && /^## \[/ { exit } + on { print } + ' CHANGELOG.md > "$RUNNER_TEMP/notes.md" + if [ ! -s "$RUNNER_TEMP/notes.md" ]; then + echo "::error::CHANGELOG.md has no section for $v" + exit 1 + fi + + - name: Create tag and release + if: steps.exists.outputs.skip != 'true' + env: + GH_TOKEN: ${{ github.token }} + run: | + gh release create "${{ steps.version.outputs.tag }}" \ + --target "$GITHUB_SHA" \ + --title "Agentic Attack Index ${{ steps.version.outputs.tag }}" \ + --notes-file "$RUNNER_TEMP/notes.md" \ + dist/incidents.json dist/incidents.ndjson dist/incidents.csv \ + dist/summary.json dist/stix/bundle.json schema/incident.schema.json diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f728b72..857d2f5 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -53,6 +53,15 @@ Update the fields, add the new source(s), bump `last_updated`, and keep the `id` - Trust-critical paths (`data/`, `schema/`, `taxonomy/`, `scripts/`, `.github/`) have code owners (`.github/CODEOWNERS`). For this to actually gate merges, enable branch protection on `main` with **Require a pull request before merging**, **Require review from Code Owners**, and **Require status checks to pass** (select the `validate + build` check) — these are GitHub repo settings, not files in the repo. - If you change `schema/`, update `README.md`, the taxonomy files, and `CITATION.cff` as needed, and explain the migration in the PR. +## Releasing + +The dataset follows semantic versioning: added records or enum values are a minor bump; a removed or renamed field or enum value is a major bump with a migration note. To cut a release: + +1. On a `release/vX.Y.Z` branch, set the same version in `package.json` (`npm version X.Y.Z --no-git-tag-version`, which also updates `package-lock.json`) and in `CITATION.cff`, along with `date-released`. +2. Move the `[Unreleased]` notes in `CHANGELOG.md` into a dated `[X.Y.Z]` section. +3. Run `npm test` and `npm run linkcheck`, commit the rebuilt `dist/` as `chore(release): vX.Y.Z`, and open a PR. +4. After the merge, `.github/workflows/release.yml` creates the `vX.Y.Z` tag and a GitHub Release. The release notes come from the changelog section, and the `dist/` artifacts and schema are attached. The workflow fails if that section is missing. + ## Licensing of contributions By contributing you agree that data contributions are licensed CC BY-SA 4.0 and code contributions MIT (see `LICENSE-data` and `LICENSE`). From d376705e3fe548da5b68534a4d167e0a903e856a Mon Sep 17 00:00:00 2001 From: RiccardoBiosas Date: Thu, 15 Oct 2026 15:26:22 +0700 Subject: [PATCH 2/2] chore(release): v0.5.0 Bumps package.json and CITATION.cff from 0.4.0 to 0.5.0 (date-released 2026-10-15) and adds the missing CHANGELOG section for the 2026-10-15 intake sweep (#16: 14 new records, 13 updated, RubyGems record disputed). Rebuilds dist/ so the version stamp reads 0.5.0. This is an additive minor bump with no schema change. npm test passes: 96 records (95 active), 16/16 tests. Co-Authored-By: Claude Opus 5.5 --- CHANGELOG.md | 62 +++++++++++++++++++++++++++++++++++++++++++++++ CITATION.cff | 4 +-- dist/index.html | 4 +-- dist/summary.json | 2 +- package-lock.json | 4 +-- package.json | 2 +- 6 files changed, 70 insertions(+), 8 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index d131f1b..6e20cc1 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,68 @@ dataset version tracks `package.json` and `CITATION.cff` (kept in sync by ## [Unreleased] +## [0.5.0] - 2026-10-15 + +### Added +- Release workflow (`.github/workflows/release.yml`): when a version bump + lands on `main`, it creates the `v` git tag and a GitHub Release + whose notes are this changelog's section for that version, with the `dist/` + artifacts and the JSON Schema attached. Until now no release was tagged, so + consumers could not pin a version. `v0.4.0` was tagged retroactively at its + release commit. The release steps are documented in CONTRIBUTING. + +### Data +- Intake sweep of 2026-10-15 (#16): 14 incidents, each re-validated against + its full primary source for publisher authenticity, corroboration, + counter-evidence, scope and duplicates. The catalog grows from 82 to 96 + records; 95 are active. + - **Agent-driven intrusion campaigns:** + `artex-south-korea-finance-intrusions` (CrowdStrike; ARTEX agentic + pentest tool and Claude Code sessions against South Korean financial + institutions), + `cyberxero-ai-augmented-access-broker` (SOCRadar; Claude Code agent swarm + alongside intrusions at Ukrainian utilities), + `mexico-government-claude-code-intrusions` (Gambit Security; disputed by + the agencies concerned, none named), + `gambit-gentlemen-affiliate-claude-code-intrusions`, + `oalabs-compromised-server-claude-codex-intrusions`, + `unit42-hermes-deepseek-autonomous-campaign` (ATLAS `AML.CS0070`), + `gtig-recon-agentic-secret-harvesting`, + `storm-3168-azure-service-principal-destruction` (Microsoft; `ai_role: + disputed`). + - **Evaluation and research agents that reached real third parties:** + `anthropic-unintended-model-actions-real-websites`, + `openai-agents-australian-state-agencies`, + `ai-agents-us-canada-government-websites` (Transluce; actor Unknown). + - **AI-agent supply chain:** + `mandiant-hijacked-coding-assistant-shai-hulud`, + `skills-sh-paperclip-malicious-skills`, + `postmark-mcp-bcc-backdoor`. + +### Changed +- `openai-attributed-rubygems-agent-swarm` is now `record_status: disputed`. + OpenAI says it has not been able to verify that its models uploaded the + malicious packages, and RubyGems cannot confirm AI involvement. Disputed + records are excluded from headline counts. +- Confidence raised from secondary to primary on + `openai-attributed-dsewiki-agent-swarm` and + `openai-huggingface-may-account-hijacking`, after OpenAI's first-party + notices and technical report were cited. The DseWiki start date was + corrected. +- `jadepuffer-agentic-database-extortion`: `autonomy_level` changed from + unknown to supervised-autonomous, per Sysdig's clarification that a human + set up and targeted the operation. Linked to the new Storm-3168 record. +- `openai-long-horizon-sandbox-escape-github-pr`: added OpenAI's GitHub-token + report and corrected the "no third-party victim" wording. + `openai-agent-services-australia-medicare-portal`: a TODO is now closed + with OpenAI's first-party post. +- MITRE ATLAS case-study ids (v2026.09) added to `echoleak-m365-copilot`, + `radware-zombieagent-deep-research`, + `openai-eval-agents-hugging-face-intrusion`, `gtg-1002-ai-espionage` and + `dream-multi-agent-asia-government-campaign`. Also added: CISA KEV notes on + `divd-zammad-ai-agent-breach` and `papercut-agentic-global-intrusion`, and + the MODA press release as a source on the Dream record. + ## [0.4.0] - 2026-10-11 ### Added diff --git a/CITATION.cff b/CITATION.cff index db2d099..02a9829 100644 --- a/CITATION.cff +++ b/CITATION.cff @@ -10,8 +10,8 @@ authors: website: "https://mlsecopshub.com" repository-code: "https://github.com/MLSecOpsHub/agentic-attack-index" url: "https://mlsecopshub.com" -version: 0.4.0 -date-released: 2026-10-11 +version: 0.5.0 +date-released: 2026-10-15 license: CC-BY-SA-4.0 keywords: - ai-security diff --git a/dist/index.html b/dist/index.html index 0f365ec..9950006 100644 --- a/dist/index.html +++ b/dist/index.html @@ -3,7 +3,7 @@ -Agentic Attack Index — dataset 0.4.0 +Agentic Attack Index — dataset 0.5.0