[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M721074WPAC6W82S3BYXZECE":3,"skill-same:01M721074WPAC6W82S3BYXZECE":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M721074WPAC6W82S3BYXZECE","defi-admin-takeover-mitigation-lessons",null,"Mitigation patterns for privileged-access and governance-adjacent DeFi failures, anchored on the public Drift Protocol incident analysis in Chainalysis’s blog-social engineering, Solana durable nonces, oracle and collateral abuse, multisig governance, and operational monitoring. Use when hardening signer processes, reviewing admin surfaces, or teaching post-incident lessons-not for designing exploits or attributing actors without evidence.","zkos-labs\u002Fbastion","zkos-labs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263369112?v=4","01M720WZH0GD7FAKBP5PSGF4TG","ZKOS Labs","01M720WZHP9JV5NZVQCHA6XJ3M",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdefi-admin-takeover-mitigation-lessons\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: defi-admin-takeover-mitigation-lessons\ndescription: Mitigation patterns for privileged-access and governance-adjacent DeFi failures, anchored on the public Drift Protocol incident analysis in Chainalysis’s blog-social engineering, Solana durable nonces, oracle and collateral abuse, multisig governance, and operational monitoring. Use when hardening signer processes, reviewing admin surfaces, or teaching post-incident lessons-not for designing exploits or attributing actors without evidence.\n---\n\n# DeFi admin takeover - mitigation lessons (case-informed)\n\n**Educational reference.** Primary public narrative for the **Drift Protocol** incident (April 2026, ~USD 285M scale reported) is summarized in Chainalysis’s post [“The Drift Protocol Hack: How Privileged Access Led to a $285 Million Loss”](https:\u002F\u002Fwww.chainalysis.com\u002Fblog\u002Flessons-from-the-drift-hack\u002F). **Attribution** (for example DPRK-linked) and **mechanics** details there rely on **Drift’s investigation** and **journalism**-treat as **hypotheses** until **independent** reviews and **legal** processes conclude. This skill extracts **defensive** patterns, not gossip.\n\n## What went wrong (pattern summary)\n\nPer the public writeup, the failure mode combined **people**, **governance**, and **chain features**:\n\n1. **Long-running social engineering** - actors allegedly posed as a legitimate counterparty, built trust over months, and used normal-looking product engagement.\n2. **Synthetic collateral narrative** - a **new token** with **thin liquidity**, **wash-traded** volume, and a **controllable oracle** can look “priced” to automated systems.\n3. **Pre-signed or deferred execution** - Solana **durable nonces** allow **sign-now, execute-later** flows. If signers **do not** fully understand payloads, **blind signing** approves **authority transfers** that later execute as **valid** transactions.\n4. **Governance \u002F multisig changes** - tightening **thresholds** or **removing timelocks** without compensating **controls** can shrink the window to detect bad admin updates.\n5. **Valid signatures, malicious intent** - on-chain validation passes because **signers were real**; **semantics** of instructions were wrong.\n\n## Mitigation playbook (by layer)\n\n### 1. Signer and governance process\n\n- **No blind signing** on multisig or council transactions-require **decoded** previews, **simulation**, and **human-readable** intent for every **permission** change.\n- **Separate duties** between **who** proposes admin changes and **who** approves; use **delays** (timelocks) for **irreversible** moves unless an **emergency** path is **narrowly** scoped.\n- **Vendor and counterparty verification** independent of conference rapport-**legal** entity checks, **reference** calls, and **phishing**-resistant channels for high-risk approvals.\n- **Re-verify** multisig migrations: **threshold**, **participants**, **timelock**, and **upgrade** paths after **any** governance change.\n\n### 2. Solana-specific (durable nonces and scheduling)\n\n- Treat **durable nonce** transactions as **high risk**: maintain an **allowlist** of **instruction types** signers may pre-approve; **reject** broad **admin** transfers to **new** addresses without **out-of-band** verification.\n- Prefer **short-lived** approvals or **two-step** transfers (propose → execute after delay) where architecture allows.\n- Log and **monitor** nonce accounts tied to **privileged** signers; alert on **unexpected** nonce creation or **association** with new programs.\n\n### 3. Collateral, oracles, and risk parameters\n\n- **New asset listing** should require **liquidity depth**, **source** of price feeds, **diversity** of oracles, and **manual** review-not only **automated** listings.\n- **Caps** and **per-asset** borrow limits for **young** or **thin** markets; **circuit breakers** on **sudden** parameter changes.\n- **Oracle** integrity: detect **single-source** dominance, **owner-controlled** feeds, and **price** divergence from **liquid** venues.\n\n### 4. Runtime monitoring and response\n\n- **Alert** on **admin** role changes, **authority** transfers, **collateral** whitelist edits, and **large** coordinated **withdrawals** shortly after **governance** events.\n- **Velocity** limits on **outflows** per **time window**; **pause** hooks that **independent** monitors can trigger (not only **EOA** admins).\n- **Intent-based** or **simulation-based** guards (commercial tools exist; evaluate **fit** to your **threat model**) that flag **semantically** abnormal txs **before** execution-not only “who signed.”\n\n### 5. Ecosystem and composability\n\n- **Dependencies** on **shared liquidity** or **vaults** can **amplify** losses-map **downstream** protocols and **pause** \u002F **isolate** when **upstream** risk spikes.\n\n## Investigation and post-incident learning\n\n- Use **on-chain** timelines (tx hashes, program IDs, authority accounts) for **reconstruction**; pair **solana-tracing-specialist** with **cross-chain-clustering-techniques-agent** when funds **bridge** out.\n- For **protocol** reviews, combine **defi-security-audit-agent** and **solana-defi-vulnerability-analyst-agent** with this **process** layer.\n\n## Guardrails\n\n- **Do not** use this skill to **plan** or **optimize** attacks, **social engineer** teams, or **harass** individuals named in media.\n- **Do not** treat blog **attribution** as **legal** fact.\n- **Do not** paste **non-public** incident data, **keys**, or **customer** details into shared chats.\n\n## Source\n\n- Chainalysis - [The Drift Protocol Hack: How Privileged Access Led to a $285 Million Loss](https:\u002F\u002Fwww.chainalysis.com\u002Fblog\u002Flessons-from-the-drift-hack\u002F) (April 9, 2026; informational; not legal or investment advice).\n\n**Goal:** turn a **public** case study into **actionable** defensive habits for **teams** operating **privileged** DeFi infrastructure-especially where **signatures** are **valid** but **intent** is wrong.\n","# DeFi admin takeover - mitigation lessons (case-informed)\n\n**Educational reference.** Primary public narrative for the **Drift Protocol** incident (April 2026, ~USD 285M scale reported) is summarized in Chainalysis’s post [“The Drift Protocol Hack: How Privileged Access Led to a $285 Million Loss”](https:\u002F\u002Fwww.chainalysis.com\u002Fblog\u002Flessons-from-the-drift-hack\u002F). **Attribution** (for example DPRK-linked) and **mechanics** details there rely on **Drift’s investigation** and **journalism**-treat as **hypotheses** until **independent** reviews and **legal** processes conclude. This skill extracts **defensive** patterns, not gossip.\n\n## What went wrong (pattern summary)\n\nPer the public writeup, the failure mode combined **people**, **governance**, and **chain features**:\n\n1. **Long-running social engineering** - actors allegedly posed as a legitimate counterparty, built trust over months, and used normal-looking product engagement.\n2. **Synthetic collateral narrative** - a **new token** with **thin liquidity**, **wash-traded** volume, and a **controllable oracle** can look “priced” to automated systems.\n3. **Pre-signed or deferred execution** - Solana **durable nonces** allow **sign-now, execute-later** flows. If signers **do not** fully understand payloads, **blind signing** approves **authority transfers** that later execute as **valid** transactions.\n4. **Governance \u002F multisig changes** - tightening **thresholds** or **removing timelocks** without compensating **controls** can shrink the window to detect bad admin updates.\n5. **Valid signatures, malicious intent** - on-chain validation passes because **signers were real**; **semantics** of instructions were wrong.\n\n## Mitigation playbook (by layer)\n\n### 1. Signer and governance process\n\n- **No blind signing** on multisig or council transactions-require **decoded** previews, **simulation**, and **human-readable** intent for every **permission** change.\n- **Separate duties** between **who** proposes admin changes and **who** approves; use **delays** (timelocks) for **irreversible** moves unless an **emergency** path is **narrowly** scoped.\n- **Vendor and counterparty verification** independent of conference rapport-**legal** entity checks, **reference** calls, and **phishing**-resistant channels for high-risk approvals.\n- **Re-verify** multisig migrations: **threshold**, **participants**, **timelock**, and **upgrade** paths after **any** governance change.\n\n### 2. Solana-specific (durable nonces and scheduling)\n\n- Treat **durable nonce** transactions as **high risk**: maintain an **allowlist** of **instruction types** signers may pre-approve; **reject** broad **admin** transfers to **new** addresses without **out-of-band** verification.\n- Prefer **short-lived** approvals or **two-step** transfers (propose → execute after delay) where architecture allows.\n- Log and **monitor** nonce accounts tied to **privileged** signers; alert on **unexpected** nonce creation or **association** with new programs.\n\n### 3. Collateral, oracles, and risk parameters\n\n- **New asset listing** should require **liquidity depth**, **source** of price feeds, **diversity** of oracles, and **manual** review-not only **automated** listings.\n- **Caps** and **per-asset** borrow limits for **young** or **thin** markets; **circuit breakers** on **sudden** parameter changes.\n- **Oracle** integrity: detect **single-source** dominance, **owner-controlled** feeds, and **price** divergence from **liquid** venues.\n\n### 4. Runtime monitoring and response\n\n- **Alert** on **admin** role changes, **authority** transfers, **collateral** whitelist edits, and **large** coordinated **withdrawals** shortly after **governance** events.\n- **Velocity** limits on **outflows** per **time window**; **pause** hooks that **independent** monitors can trigger (not only **EOA** admins).\n- **Intent-based** or **simulation-based** guards (commercial tools exist; evaluate **fit** to your **threat model**) that flag **semantically** abnormal txs **before** execution-not only “who signed.”\n\n### 5. Ecosystem and composability\n\n- **Dependencies** on **shared liquidity** or **vaults** can **amplify** losses-map **downstream** protocols and **pause** \u002F **isolate** when **upstream** risk spikes.\n\n## Investigation and post-incident learning\n\n- Use **on-chain** timelines (tx hashes, program IDs, authority accounts) for **reconstruction**; pair **solana-tracing-specialist** with **cross-chain-clustering-techniques-agent** when funds **bridge** out.\n- For **protocol** reviews, combine **defi-security-audit-agent** and **solana-defi-vulnerability-analyst-agent** with this **process** layer.\n\n## Guardrails\n\n- **Do not** use this skill to **plan** or **optimize** attacks, **social engineer** teams, or **harass** individuals named in media.\n- **Do not** treat blog **attribution** as **legal** fact.\n- **Do not** paste **non-public** incident data, **keys**, or **customer** details into shared chats.\n\n## Source\n\n- Chainalysis - [The Drift Protocol Hack: How Privileged Access Led to a $285 Million Loss](https:\u002F\u002Fwww.chainalysis.com\u002Fblog\u002Flessons-from-the-drift-hack\u002F) (April 9, 2026; informational; not legal or investment advice).\n\n**Goal:** turn a **public** case study into **actionable** defensive habits for **teams** operating **privileged** DeFi infrastructure-especially where **signatures** are **valid** but **intent** is wrong.\n",{"name":5,"description":7},"main","d10fe79c634de337daa2ad2fa82857c8a743616b",".agents\u002Fskills\u002Fdefi-admin-takeover-mitigation-lessons",1,"https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion","https:\u002F\u002Fbastionagentique.com\u002F","https:\u002F\u002Fgithub.com\u002Fzkos-labs","https:\u002F\u002Fzkoslabs.org","A research-driven builders' organization advancing programmable trust infrastructure for Ethereum and interoperable open networks.","2026-11-13 21:01:45",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add zkos-labs\u002Fbastion --skill defi-admin-takeover-mitigation-lessons",{"tool":40,"command":41},"bunx","bunx skills add zkos-labs\u002Fbastion --skill defi-admin-takeover-mitigation-lessons",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zkos-labs\u002Fbastion --skill defi-admin-takeover-mitigation-lessons","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdefi-admin-takeover-mitigation-lessons\u002FSKILL.md",true,[],[49,57,64,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":53,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7213RCWV886P2R63MTQAEGW","bastion","Programmable Trust Runtime for Autonomous Systems. Orchestrates identity, policy, privacy, durable execution, and multi-chain settlement.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7213MYSJE23KMMTD95Y3M3Z","web2-api-firewall-administrator","Guides configuring Bastion Web2 API adapter policies for the Trust Runtime. Covers endpoint allowlists, provider budgets, rate limits, content inspection (PII\u002Fsecrets detection), header filters, and OpenAPI spec-based auto-configuration. Use when configuring API call security for AI agents, setting provider spending caps, inspecting outbound API traffic, or setting up the Web2 adapter.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb2-api-firewall-administrator\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7213HE08PE43M2H0QZENZP2","transaction-screening-workflow-concepts","Educational map of transaction-centric compliance screening-transfer as the atomic unit, deposit vs withdrawal direction, single and CSV import, transaction list and detail views, per-transfer screening, rescreen, and STR-style exports. Use when the user asks how monitoring UIs treat tx hashes, directions, or regulatory reporting hooks-not for legal filing advice or evading reporting.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftransaction-screening-workflow-concepts\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7213DQ7TVE986643SR105Y4","solana-tracing-specialist","Guides Solana-specific on-chain forensics-ATA resolution, SPL instruction parsing, transaction history via RPC and indexers (e.g. Helius-style APIs), fund-flow graphs, Solana clustering heuristics, and program authority review. Use when the user investigates Solana wallets, SPL tokens, DEX\u002FJito flows, rug or phishing patterns on Solana, or needs evidence-structured tracing reports with public data only.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-tracing-specialist\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M72138PB2HTKJ0J39WNSRCRR","solana-onchain-intelligence-resources","Companion to blockint-skills Solana work-official doc indexes and stacks for RPC\u002Findexers, sanctions and address intel MCP, web research, agent payments, graph UIs, Solana Foundation dev skills, Solana Policy Institute (policy\u002Fregulatory education), optional open-source Scrapy collection (BlockchainSpider), Impersonator Solana (dApp dev\u002Ftesting), coral-xyz sealevel-attacks (security pattern examples), Neodyme Solana Security Workshop (workshop.neodyme.io), and Osec Solana auditor introduction blog (osec.io). Use when the user needs pointers to Helius, Range AI, Tavily, PayAI x402, React Flow, Solana.com skills, or SPI alongside on-chain forensics-not as a substitute for reading current provider docs, legal counsel, or API keys.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-onchain-intelligence-resources\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M72134Y4PVHN6CQPHX9NKSHQ","solana-defi-vulnerability-analyst-agent","Guides discovery and documentation of Solana DeFi protocol risks from public code and chain state-Anchor\u002Fnative programs, PDAs, CPIs, oracles, pools, SPL mechanics, and historical tx reconstruction. Use when the user asks for Solana program security review, DeFi vulnerability triage, PDA or CPI safety, oracle or liquidity-pool risk, launchpad\u002Fbonding-curve issues, or evidence-backed severity findings without exploits or private keys.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-defi-vulnerability-analyst-agent\u002FSKILL.md",[],[]]