Skip to main content
If you believe you have found a security issue in Agent Vault, report it privately using the process on this page. We review every report.

​
How to report

Email team@self.xyz. The same contact is published at https://agentvault.io/.well-known/security.txt. Please do not open a public GitHub issue for a security problem, and do not disclose it publicly until we have had the opportunity to respond.

​
What to include

1

What you found

One or two sentences describing the issue.
2

How to reproduce it

Concrete steps: a request, a sequence of tool calls or a minimal script, with the time you observed it.
3

The impact

What an attacker gains, stated plainly. This determines severity.
4

Anything you know about a fix

Optional, and always welcome.
Do not include real card numbers, CVVs or passwords in a report. If a reproduction needs card data, use a test card and say so.

​
Scope

​
In scope

Any issue that breaks a property Agent Vault states in its security documentation:

A real value reaching the agent

Any path by which an agent can read a substituted card number, CVV, password, authenticator secret or code.

A credential resolving off-site

Any way to make a login token resolve on a host it is not registered for, or a card token resolve against its agent card rules.

Crossing accounts

Any way for one account’s key or session to resolve another account’s resource.

Bypassing a spending control

Spending past a cap, a merchant rule or an approval threshold.

Escaping key scope

A scoped key resolving a resource outside its scope.

Values in records

A substituted value appearing in a session event, a receipt, a log or an analytics payload.

Instructions in data we serve

Text in a checkout recipe, or any other data served to agents, that instructs the reading agent.

Prompt link misuse

An approval, CVV or challenge link that works when it should not, for example after it expired or after account deletion.

​
Where you may test

Use your own account, a test card and the practice checkout at https://app.agentvault.io/demo-checkout wherever you can. A self-hosted deployment is its owner’s to authorize, not ours. Not in scope, and not something we can authorize:
  • Any merchant website, including through an Agent Vault session. You would be testing a system we do not own.
  • The third-party providers Agent Vault is built on: the card vault, sign-in, hosting, billing and email providers. Report an issue in one of them to that provider.
  • Social engineering, physical access and denial of service.

​
Out of scope

The following are documented design decisions rather than defects. If you believe one of these decisions is wrong rather than merely deliberate, tell us. A documented decision can still be a poor one.

​
Testing responsibly

  • Test only against your own account, cards and logins.
  • Do not access, modify or delete data that is not yours. If you reach another account’s data by accident, stop, and include that in your report.
  • Do not run load or denial-of-service tests.
  • Use test cards where possible. Where a real purchase is unavoidable, use the smallest amount possible: merchants are real businesses.
  • Give us reasonable time to fix an issue before any public disclosure.

​
Safe harbor

Security research carried out in good faith and within this policy is authorized. For such research, SocialConnect Labs, Inc., doing business as Self Labs, the company behind Agent Vault:
  • will not bring a civil claim against you, and will not refer you to law enforcement, for an accidental, good-faith breach of this policy;
  • treats your research as authorized under computer misuse laws, such as the US Computer Fraud and Abuse Act, and will not bring a claim under anti-circumvention laws, such as the DMCA, for bypassing a technical control as far as your research needed;
  • will make it known that you acted within this policy, if a third party brings legal action against you for research that did.
This covers our own rights only. We cannot authorize testing of systems we do not own, so merchant websites and our providers are not covered: see Where you may test. You are still expected to comply with the law. If you are unsure whether something is covered, ask at team@self.xyz before you start.

​
What to expect

These are targets, not guarantees. When we miss one, we tell you why and give you a new date.

​
Rewards

We do not run a bug bounty program and do not pay for reports. We credit you, by name or handle, on request once the fix is deployed.

​
Coordinated disclosure

We will agree a disclosure timeline with you. Our aim is a deployed fix before any public write-up, and we would rather agree a date with you than ask for an open-ended delay. If 90 days pass from your report without a deployed fix, you may publish. Tell us the date first, so we can publish our own account alongside yours.

Security model

What Agent Vault protects, and where its protection ends.

URL locking

The anti-phishing control, and its deliberate ambiguities.