The Recourse team takes the security of our smart contracts, cryptographic verification pipelines, and off-chain execution services seriously. We appreciate responsible disclosure from security researchers and community contributors.
Recourse is actively developed on the main branch. Security fixes and patches are applied directly to the active codebase.
| Branch / Release | Supported | Status |
|---|---|---|
main |
✅ | Active development & primary target |
| Older releases | ❌ | Unsupported; please upgrade to main |
Please do not report security vulnerabilities through public GitHub issues, pull requests, or public discussions.
When enabled by repository administrators or upon public repository launch, the preferred channel for disclosing vulnerabilities is GitHub Private Vulnerability Reporting:
This feature provides a private, encrypted environment for collaborating directly with maintainers on verification and patch development.
Because this repository is currently in pre-release development, the native GitHub Security Advisory submission form may not be accessible to external accounts without repository invitation.
If the Advisory form is inaccessible or returns an authorization error:
- Do NOT open a public issue or pull request.
- Please reach out privately to the repository maintainers via their GitHub profiles:
- Dev Prashant (@devprashant19)
- Puneet Yadav (@puneetnith28)
- Request a private communication channel (such as a secure one-to-one channel or temporary private fork invitation) before sharing any technical details, proof-of-concept scripts, or reproduction steps.
To help us investigate and remediate the issue quickly, please include:
- Summary: A concise description of the vulnerability and its potential impact.
- Affected Component(s):
- NEAR smart contracts (
contracts/recourse/,contracts/test-token/) - Cryptographic verification & TEE receipts (
packages/receipts/,packages/sdk/) - Arbiter & LLM rubric evaluation (
services/arbiter/) - Keeper execution & lease coordination (
services/keeper/) - Event indexer & audit ledger (
services/indexer/) - Web application (
apps/web/)
- NEAR smart contracts (
- Reproduction Steps: A clear, step-by-step proof-of-concept (PoC) or script reproducing the vulnerability.
- Impact Assessment: Explanation of what an attacker could achieve (e.g., unauthorized slashing, drain of vault funds, spoofed TEE receipt, lease hijacking).
- Mitigation Suggestions: Any recommended code changes or configuration fixes (optional).
| Severity | Components & Scenarios |
|---|---|
| Critical | Vulnerabilities in on-chain contract logic (contracts/recourse/) leading to fund loss, unauthorized payouts, balance manipulation, broken solvency invariants, or bypassing ecrecover TEE signature checks. |
| High | Bypassing generation-fenced keeper lease coordination, tampered audit-chain ledger generation, or prompt-injection vulnerabilities that force arbiter receipts to produce invalid verdicts without detection. |
| Medium | Denial of Service in indexing pipelines, unauthenticated administrative access to sabotage endpoints in production modes, or state reconciliation failure after service restarts. |
| Low / Informational | Frontend presentation bugs, non-exploitable race conditions, or minor documentation discrepancies. |
Caution
Never include real private keys, NEAR testnet/mainnet account credentials, secret seed phrases, or production service tokens in vulnerability reports, pull requests, or public issues.
When demonstrating an exploit or vulnerability, always use sandbox accounts, dummy private keys, or standard test fixtures.
If you accidentally commit or expose a private key, NEAR account credentials, API secret, or service token:
- Rotate and Revoke Immediately: Treat the exposed secret as compromised. Immediately revoke or rotate the credential at the provider or NEAR account level.
- Do Not Rely on
git rm: Deleting the key in a subsequent commit leaves the secret in the Git history. - Notify Maintainers: Report the incident privately via GitHub Security Advisories so maintainers can rewrite or scrub repository history if necessary.
To protect users and the integrity of the protocol:
- Private Reporting Only: Do not discuss or disclose vulnerability details publicly, in GitHub issues, or in pull requests before maintainers have investigated and patched the issue.
- No Exploitation on Live Networks: Do not attempt attacks or exploits against live NEAR testnet or mainnet accounts. Always demonstrate proof-of-concept exploits against local sandbox environments (
RECOURSE_MODE=sandbox). - Constructive Communication: Give maintainers reasonable time to analyze the finding, prepare a fix, and coordinate release.
- Acknowledgment: Maintainers will review and acknowledge received security advisories promptly.
- Triage & Validation: Maintainers will validate the reported issue and determine its severity and blast radius.
- Coordination & Patching: A fix will be developed privately in a temporary private fork.
- Disclosure: Once the patch is merged and deployed, a public security advisory will be published crediting the reporter (unless anonymity is requested).