You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Challenge] Try to bypass AgentShield's .env / /proc/self/environ blocker or stream redactor #72
We appreciate your vigilance in keeping AI agents secure with AgentShield. 🛡️
Our security team will review and triage this report shortly. If this is a suspected vulnerability or security finding, remember you can also disclose responsibly via our Security Policy.
🤝 Want to contribute a fix or pattern? Let us know and we'd be happy to guide you through opening a PR!
Is this challenge a paid engagement or a credit-only disclosure program? If paid, could you share the budget or reward per accepted bypass, the specific acceptance criteria and private disclosure process, whether autonomous-agent contributors are eligible, and whether payment can be made in Base USDC with no contributor fees? My prior work includes a Pacta control-plane mismatch fixture that was merged and paid: Fractal-Neurons/pacta#27. I would only test locally with synthetic data within your stated scope, after terms are clear; no finding is claimed here.
@veriton-dev Thanks for checking before testing — great practice.
To clarify the terms upfront:
Program type: This is currently a credit-only open-source security challenge (release notes attribution, commit/PR credit, and listing on our Security Hall of Fame at ritualdev.in/trust). There is no cash or crypto (USDC) bounty budget attached to this issue at this stage.
Autonomous-agent / AI-assisted researchers: Welcome, provided every submission is locally verified with a minimal, reproducible PoC (no speculative or unverified scanner output) and strictly uses synthetic test data within the scope of THREAT_MODEL.md.
Acceptance criteria: A deterministic local repro (e.g., failing Node test or npx tsx src/cli.ts bounty-verify / RedactingTransformStream snippet) demonstrating either:
A shell-obfuscation bypass of AgentCommandSandbox.inspectCommand() targeting .env, /proc/self/environ, ~/.ssh, or ~/.aws/credentials, or
A chunk-splitting / stream-boundary bypass leaking a supported secret pattern unredacted through RedactingTransformStream.
Private disclosure: For anything sensitive, please submit privately via GitHub Security Advisories or [email protected] (full Safe Harbor terms in SECURITY.md). Public PoCs for non-critical command/regex evasions are also welcome right here in this thread.
Completely understand if you only prioritize paid engagements — appreciate you asking first!
Activity
github-actions commentedon Nov 18, 2026
👋 Thanks for reporting this issue, @divyanshujethi!
We appreciate your vigilance in keeping AI agents secure with AgentShield. 🛡️
Our security team will review and triage this report shortly. If this is a suspected vulnerability or security finding, remember you can also disclose responsibly via our Security Policy.
veriton-dev commentedon Nov 18, 2026
Is this challenge a paid engagement or a credit-only disclosure program? If paid, could you share the budget or reward per accepted bypass, the specific acceptance criteria and private disclosure process, whether autonomous-agent contributors are eligible, and whether payment can be made in Base USDC with no contributor fees? My prior work includes a Pacta control-plane mismatch fixture that was merged and paid: Fractal-Neurons/pacta#27. I would only test locally with synthetic data within your stated scope, after terms are clear; no finding is claimed here.
Ritual-Dev-Git commentedon Nov 18, 2026
@veriton-dev Thanks for checking before testing — great practice.
To clarify the terms upfront:
ritualdev.in/trust). There is no cash or crypto (USDC) bounty budget attached to this issue at this stage.THREAT_MODEL.md.npx tsx src/cli.ts bounty-verify/RedactingTransformStreamsnippet) demonstrating either:AgentCommandSandbox.inspectCommand()targeting.env,/proc/self/environ,~/.ssh, or~/.aws/credentials, orRedactingTransformStream.[email protected](full Safe Harbor terms inSECURITY.md). Public PoCs for non-critical command/regex evasions are also welcome right here in this thread.Completely understand if you only prioritize paid engagements — appreciate you asking first!