Skip to content

feat(security): add E2E security test harness with channel ingress testing#3923

Closed
jai wants to merge 7 commits into
openclaw:mainfrom
jai:feat/security-test-harness
Closed

feat(security): add E2E security test harness with channel ingress testing#3923
jai wants to merge 7 commits into
openclaw:mainfrom
jai:feat/security-test-harness

Conversation

@jai

@jai jai commented Jan 29, 2026

Copy link
Copy Markdown
Contributor

Summary

  • E2E security test harness using LLM-as-judge pattern to detect prompt injection attacks
  • chat.ingress gateway method for testing real Telegram/WhatsApp message parsing
  • Channel tests now exercise actual ingress pipelines, access control, and group gating

Test Plan

  • pnpm test passes
  • pnpm lint passes
  • Manual testing with live gateway (in progress)

Notes

  • 🤖 AI-assisted (Claude Code) - fully tested locally
  • Work in progress - additional test coverage being added
  • See test/security/SPEC.md for full design

jai added 6 commits January 29, 2026 08:52
Add comprehensive security acceptance testing framework that validates
Moltbot's resistance to prompt injection, data exfiltration, and trust
boundary violations.

Key components:
- LLM-as-judge pattern using Claude to evaluate attack resistance
- WebSocket gateway client for direct protocol testing
- CLI mocking utilities for injecting poisoned external data
- Docker Compose setup for containerized CI execution
- GitHub Actions workflow with daily scheduled runs

Test categories covered:
- Email/calendar prompt injection via external data
- Trust boundary violations and auth bypass attempts
- Data exfiltration prevention
- Tool output poisoning
Break down SPEC.md into actionable specification documents:
- 00-overview: Architecture and test flow
- 01-llm-judge: Claude evaluation interface and requirements
- 02-gateway-client: WebSocket protocol (needs discovery)
- 03-cli-mocks: PATH interception strategy and payloads
- 04-test-categories: All attack vectors with test cases
- 05-ci-docker: Container and CI configuration
- 06-implementation-plan: Phased rollout with next steps
@openclaw-barnacle openclaw-barnacle Bot added channel: telegram Channel integration: telegram channel: whatsapp-web Channel integration: whatsapp-web app: web-ui App: web-ui gateway Gateway runtime labels Jan 29, 2026
@sebslight

Copy link
Copy Markdown
Contributor

Closing: Large PRs (1000+ lines) require prior alignment with maintainers before submission. Please:

  1. Open an issue first to discuss the feature/change
  2. Get maintainer buy-in on the approach
  3. Consider breaking into smaller, reviewable PRs

We appreciate your interest in contributing, but reviewing massive unaligned PRs is not sustainable. Feel free to reopen after discussing the approach in an issue.

@jai

jai commented Jan 29, 2026

Copy link
Copy Markdown
Contributor Author

Closing: Large PRs (1000+ lines) require prior alignment with maintainers before submission. Please:

  1. Open an issue first to discuss the feature/change
  2. Get maintainer buy-in on the approach
  3. Consider breaking into smaller, reviewable PRs

We appreciate your interest in contributing, but reviewing massive unaligned PRs is not sustainable. Feel free to reopen after discussing the approach in an issue.

Thanks for the heads up.

#4011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

app: web-ui App: web-ui channel: telegram Channel integration: telegram channel: whatsapp-web Channel integration: whatsapp-web gateway Gateway runtime

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants