Skip to content

ShieldFive

Bug bounty on Self-hosted shieldfive.com

Accepting reports
Top reward
$1,000
Top severity paid
Not published
Assets in scope
13
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $1,000
top reward.
Report by email
[email protected]
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

The policy page has no reward table. Here is what it says, in its own words.

Pays cash
No There is no bounty program — the one ShieldFive ran closed in 2026-07 — but reports are triaged, fixed, and credited by name or handle if the reporter wants that.
Hall of fame
Yes Researchers who reported a vulnerability to [email protected] and asked to be credited.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

13 assets you may test, 7 excluded.

Domains 13

  • argon2id.ts
  • format-v1.md
  • header.ts
  • shieldfive.com
  • the following code and specifications, at the latest published version of @shieldfive/crypto on npm, or any version still readable from a production deployment of shieldfive.com: No bounty
  • the format header parser in src/format/header.ts No bounty
  • the four cipher suites: aes-256-gcm-v1 (suite 0x01), xchacha20-poly1305-v1 (0x02), pq-hybrid-xchacha-mlkem1024-v1 (0x03), and the read-only legacy aes-gcm-v0 reader No bounty
  • the hkdf-sha-256 and hmac-sha-256 primitives in src/internal/ No bounty
  • the identity and sharing module in src/identity/ No bounty
  • the kdf wrapper in src/kdf/argon2id.ts No bounty
  • the threat model claims in spec/threat-model.md — if you can falsify a specific claim from that document, we want to know No bounty
  • the v1 wire format as specified in spec/format-v1.md No bounty
  • threat-model.md
Out of scope (7)
  • denial-of-service against the public website or against npm registry endpoints
  • side-channel attacks against the underlying browser subtlecrypto runtime, the user's cpu microarchitecture, or libsodium's wasm build. these are documented as out-of-scope in spec/threat-model.md
  • theoretical attacks on the underlying primitives (aes, chacha20, ml-kem-1024, sha-256, argon2id) at the construction level — these belong in the academic literature
  • these are not eligible for bounty under this program. reports of these will be acknowledged and read, but will not be paid
  • the shieldfive.com web application, infrastructure, or any service shieldfive operates other than the crypto library. the web application is not yet open-source and is not yet eligible for a public bounty; we plan to extend the program after the web application has been independently audited
  • vulnerabilities in dependencies (@noble/post-quantum, libsodium-wrappers-sumo, node.js, browsers, v8, jsc, webkit) — please report those upstream
  • vulnerabilities that require an attacker to already control the user's device (malware, malicious browser extensions, keyloggers)

Changes

Tracked since 11 Nov 2026. Last checked 5 hours ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.