Senior Hive Member - Blockchain, Cryptography & Digital Asset Offensive Security; Global

At Covert Swarm, we are redefining offensive security through constant, relentless attack. As a Senior Hive Member specialising in blockchain, encryption and digital asset security
, you will lead sophisticated offensive security engagements against the systems that move, protect, sign for and settle digital assets.

We are considering candidates from across all regions and territories, welcoming talent from across the globe.

This role is focused on environments where cryptography, blockchain infrastructure, financial systems and operational controls intersect. You will assess custody platforms, wallet infrastructure, HSM/MPC/TSS signing services, smart contracts, institutional trading APIs, stablecoin settlement rails, blockchain nodes, tokenisation platforms, cloud environments, CI/CD pipelines and the operational workflows that support them.

This is not a generic offensive security role and it is not limited to smart contract audits. You will take an adversarial view of the full digital asset ecosystem: on‑chain, off‑chain, cloud, application, cryptographic, operational and human.

Your work will help clients understand how their most valuable systems could fail under real attack conditions, including unauthorised signing, private key exposure, smart contract exploitation, API abuse, settlement failure, reconciliation breakdown, insider misuse, market disruption or irreversible asset loss.

We are looking for an experienced offensive security operator with deep technical curiosity and proven capability across blockchain, cryptography, encryption, secure protocols and complex distributed systems.

You will lead research‑led attack plans against environments similar to those used by institutional digital asset firms, market makers, OTC trading desks, custodians, stablecoin settlement providers, tokenisation platforms and Web3 product teams.

These environments commonly include:

• Institutional trading platforms using REST, Web Socket, FIX, RFQ and GUI workflows.
• Market‑making, OTC execution, post‑trade settlement and treasury operations.
• Experience in attacking communication protocols, specifically the Matrix protocol.
• Stablecoin settlement across Ethereum, Solana, Tron, L2s and other chains.
• Custody architectures involving hot, warm and cold wallets.
• HSM, KMS, MPC, threshold signing, multisig and key ceremony workflows.
• Smart contracts, token contracts, bridges, escrow, governance and DeFi mechanics.
• Cloud‑native infrastructure, Kubernetes, CI/CD, secrets management and privileged access.
• Operational approval flows, reconciliation systems, audit trails and incident response processes.

You will be expected to go beyond checklist testing. The role requires someone who can identify how a weakness in one layer—such as cloud IAM, API permissions, CI/CD secrets, wallet policy, signing workflow, approval logic or transaction monitoring—could be chained into a material compromise of digital assets.

Deep cryptography skills are essential, including the ability to review cryptographic designs, challenge trust assumptions, assess implementation weaknesses, and evaluate key management, encryption, authentication and secure messaging controls from an offensive perspective.

Strong experience with the Matrix protocol would be extremely beneficial, including federation, end‑to‑end encryption, identity, homeserver behaviour, client‑server and server‑server APIs, bridge architectures, and the security implications of decentralised messaging at scale.

You are an experienced offensive security professional who understands that digital asset security is not just about blockchain code. It is about the complete chain of trust: identity, infrastructure, code, keys, APIs, signers, policy engines, approvals, people, operations, monitoring and settlement.

You are comfortable asking difficult questions, such as:

• Can a compromised cloud role, API key, CI/CD runner or support account trigger a signing event?
• Can a transaction be altered, replayed, delayed, reordered or misrouted before approval or broadcast?
• Can wallet policies be bypassed through edge cases in asset type, chain, limit, quorum, allowlist or…