disclose.io

@disclose.io

Trademark complaint first, computer-access claim second, law enforcement third. Joshua Michael reported a Flock token exposure in 2025; now @proton.me hosts his 300,000-device camera map because its author faces legal threats. Policy Pulse #39: blog.disclose.io/policy-pulse...

Policy Pulse - Issue #39 | Week of October 25, 2026

PHP2Shell leaked three times in one night, then Bitcoin Core and curl stopped embargoing bugs a model can find. Mythos 5 kept attacking a real maintainer after being told the target was real.

blog.disclose.io

Gauteng decides this week whether to charge Joel Cedras, the student who reported that a government app's database was open to any user. "You didn't need to bypass any access controls." The department is "awaiting a report." Policy Pulse #39: blog.disclose.io/policy-pulse...

Policy Pulse - Issue #39 | Week of October 25, 2026

PHP2Shell leaked three times in one night, then Bitcoin Core and curl stopped embargoing bugs a model can find. Mythos 5 kept attacking a real maintainer after being told the target was real.

blog.disclose.io

The CISA branch chief who oversaw CVE, KEV and the CVD platform is leaving this week, and nobody has been named to replace her, per Nextgov. Same week an AI-found bug pulled ONCD and the SI Force into a disclosure chain. Policy Pulse #39: blog.disclose.io/policy-pulse...

Policy Pulse - Issue #39 | Week of October 25, 2026

PHP2Shell leaked three times in one night, then Bitcoin Core and curl stopped embargoing bugs a model can find. Mythos 5 kept attacking a real maintainer after being told the target was real.

blog.disclose.io

Told the target was a real person, Mythos 5 attacked anyway. UK AISI and Anthropic published companion analyses: once under way, the attack continued 98% of the time. The maintainer who refused the PR did a coordinator's job with none of the information. blog.disclose.io/policy-pulse...

Policy Pulse - Issue #39 | Week of October 25, 2026

PHP2Shell leaked three times in one night, then Bitcoin Core and curl stopped embargoing bugs a model can find. Mythos 5 kept attacking a real maintainer after being told the target was real.

blog.disclose.io

An embargo is a bet that the finder is the only one who knows. PHP2Shell leaked three times in one night. The same week Bitcoin Core dropped embargoes for bugs an LLM prompt can find, and curl took sub-High reports public. Policy Pulse #39: blog.disclose.io/policy-pulse...

Policy Pulse - Issue #39 | Week of October 25, 2026

PHP2Shell leaked three times in one night, then Bitcoin Core and curl stopped embargoing bugs a model can find. Mythos 5 kept attacking a real maintainer after being told the target was real.

blog.disclose.io

If you've found a broken/breached thing on the Internet and want to answer a) who the heck owns this thing and b) who should I report it to... This tool is your friend.

lookup.disclose.io passed 45,000 lookups. Our dashboard says 143,690 requests. Most of that is MCP crawlers saying hello, so after basic bot filtering we call it 45,494. 41% of 2,393 real assets resolved to a disclosure route. The rest is most of the internet having nowhere to send a report.

Look up an IP address in lookup.disclose.io and the answer is whoever is actually using it. Verified certificate subject, live redirects, and IP-hosted security.txt come first; the registered network holder and BGP origin are fallbacks; RPKI is routing context, never ownership.

Bild

The reporting contact is the first thing you see in a lookup.disclose.io result. Attribution and the evidence chain sit one section down. New below that: Historical Breadcrumbs, what the public web archive recorded for the domain, re-checked live and labeled as a lead, not ownership.

Bild

When a site's current security.txt names its disclosure platform, that wins. lookup.disclose.io drops conflicting program links from older third-party catalogs and keeps every platform the site itself publishes. No security.txt, or an expired one? Nothing gets suppressed.

Bild

security.txt results in lookup.disclose.io reflect what a site actually publishes. A TLS hostname edge case made valid files look missing on some very large sites. Fixed: /.well-known/ is checked first, an unreachable probe is not "absent," and expired files stay visible, labeled.

Bild

"Complete" in lookup.disclose.io means one thing: a reporting route qualified to the actual owner of the asset. A publisher, a repo host, a parent company, or a disclosure platform is useful context. As of September, a parent brand is context too, not disclosure scope. #AppSec

Bild

Plenty of organizations publish a solid disclosure policy that automated tools never find: behind bot protection, or deep in a help-center sitemap. lookup.disclose.io reaches those. Bunnings, TCL, and Motorola Solutions all publish one, and lookup finds it.

Bild