{"id":257,"date":"2026-08-10T07:05:31","date_gmt":"2026-08-10T07:05:31","guid":{"rendered":"https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/"},"modified":"2026-08-10T07:05:31","modified_gmt":"2026-08-10T07:05:31","slug":"what-is-exploitarium-zero-day-repository-explained","status":"publish","type":"post","link":"https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/","title":{"rendered":"What Is Exploitarium? Understanding the Zero-Day Repository"},"content":{"rendered":"

In late June 2026, a GitHub repository named exploitarium appeared containing proof-of-concept code for dozens of zero-day vulnerabilities affecting widely used open-source software. The repository was removed within days, but its contents had already been mirrored across the internet, and at least two vulnerabilities were observed being actively exploited in the wild.<\/em><\/p>\n

What Exploitarium Is<\/h2>\n

Exploitarium is a GitHub repository described as “a single archive of public exploit PoCs and vulnerability research writeups.”<\/cite> The repository was created by a researcher using the pseudonym “bikini”<\/cite> and first published on June 27, 2026, initially containing around 15 exploits before being updated over subsequent days with new entries.<\/cite><\/p>\n

The repository affected several open-source projects, including the Linux kernel, Libssh2, FFmpeg, Gogs, Gitea, Ghidra, 7-Zip, MyBB, PHP, OpenVPN, and the VLC player.<\/cite> According to the repository’s README, none of the vulnerabilities had been reported to vendors at the time of publication, and the author invited others to “report them yourself and take credit for the CVE if handed out.”<\/cite><\/p>\n

The repository’s distinguishing characteristic was not technical sophistication but deliberate timing. By publishing functional exploit code before vendors received notice, the author inverted the standard sequence of coordinated disclosure, creating a window during which attackers could weaponize the research faster than defenders could patch it.<\/p>\n

What It Contained<\/h2>\n

The researcher stated that AI was used for assistance in finding vulnerabilities but emphasized that almost all proof-of-concept code was hand-coded.<\/cite> The repository included short README files for each vulnerability, some of which were AI-generated, as were parts of the vulnerability discovery process itself.<\/cite><\/p>\n

By early July, twelve issues from the repository had received CVE identifiers, including CVE-2026-58049 (memory corruption in FFmpeg’s RASC video decoder), CVE-2026-58050 (heap buffer overflow in libssh2), CVE-2026-58052 (7-Zip failure to preserve Mark-of-the-Web warnings), and CVE-2026-58053 (host container escape in Gitea’s act_runner).<\/cite><\/p>\n

Security researcher Andrews reported that “the most technically significant findings – libssh2 pre-auth heap write and Gitea default Docker auth bypass – have been independently verified as high-risk with active exploitation observed,”<\/cite> though some disclosures “have been dismissed by the community as low-impact AI-fuzzing noise.”<\/cite><\/p>\n

The Stated Motivation<\/h2>\n

The anonymous researcher stated that the motivation behind exploitarium was recruitment, gifting findings to the public and allowing anyone to report them to affected manufacturers to “collect” a CVE, describing this approach as a way to “lure people into the field” of exploit hunting.<\/cite><\/p>\n

This rationale positions exploitarium as pedagogical rather than malicious. The repository framed itself as a public training ground, an open library where aspiring researchers could study working exploits, understand vulnerability patterns, and practice the mechanics of CVE attribution. Whether that framing withstands scrutiny depends on whether one believes recruitment justifies the operational risk introduced by publishing weaponized code without coordination.<\/p>\n

How Exploitarium Differs from Established Disclosure Practices<\/h2>\n

Vulnerability databases have existed for decades. ExploitDB, maintained by Offensive Security, has published proof-of-concept code since 2004 and contains tens of thousands of entries. The difference is timing and notification. ExploitDB publishes exploits for vulnerabilities that have already been disclosed, assigned CVE identifiers, and ideally patched. The database serves as a retrospective archive for penetration testers and researchers working against known threats.<\/p>\n

Coordinated disclosure, sometimes called responsible disclosure, operates on a different timeline. A researcher discovers a vulnerability, notifies the vendor privately, allows time for a patch to be developed and deployed, and only then publishes technical details. The delay between discovery and publication is the operational margin that allows defenders to reduce exposure before attackers gain access to exploit code.<\/p>\n

Exploitarium rejected that sequence. It published first, notified never. The operational effect was to eliminate the patch window entirely and shift the advantage decisively toward attackers. For organizations running affected software, the gap between public disclosure and available patch became a period of unmitigated risk.<\/p>\n

Why This Matters for Email Infrastructure<\/h2>\n

Email infrastructure depends on the same libraries, protocols, and tooling targeted in the exploitarium repository. OpenVPN is used to secure administrative access to mail servers. Libssh2 is embedded in Git workflows used by development teams maintaining email platforms. FFmpeg processes media attachments in webmail clients. PHP powers administrative panels and custom integrations. The vulnerabilities disclosed in exploitarium were not peripheral; they were structural dependencies.<\/p>\n

A heap overflow in libssh2, for instance, could be triggered when a mail server administrator uses an SSH client to connect to a compromised or malicious server. If that client is running on a mail server or a system with access to mail infrastructure, a successful exploit could lead to unauthorized access to email databases, configuration files, or cryptographic material. The attack surface is not always where you expect it.<\/p>\n

Email providers that rely on containerized environments for scalability, such as those using Gitea for internal tooling or CI\/CD pipelines, were directly exposed to the Gitea act_runner container escape vulnerability. An attacker who gained access to a runner could break out of the container and access the host system, potentially compromising the entire server and any email data stored on it.<\/p>\n

Architectural Considerations<\/h2>\n

The existence of repositories like exploitarium underscores a principle that applies regardless of disclosure ethics: dependencies are attack surface. Every library, every runtime, every interpreter integrated into an email platform represents a potential entry point. The longer the dependency chain, the wider the exposure.<\/p>\n

Minimizing that chain is not merely a performance optimization; it is a security posture. Platforms that operate on the principle of fewer moving parts encounter fewer vulnerabilities to track, fewer updates to apply, and fewer opportunities for an attacker to find an unpatched exploit in a transitive dependency three layers deep. Open-source post-quantum infrastructure such as PQCServer, developed under the AGPL-3.0 license, prioritizes minimal external dependencies for this reason. When every line of third-party code is a potential liability, parsimony becomes a defensive strategy.<\/p>\n

The other architectural lesson concerns update cadence. The window between exploit publication and patch deployment is where damage occurs. Organizations that can apply updates quickly, that maintain staging environments for testing, and that have rollback procedures in place are structurally more resilient to zero-day disclosures than those running static, infrequently patched infrastructure. Speed of response is an operational necessity when disclosure can happen at any time, with or without warning.<\/p>\n

The Broader Pattern<\/h2>\n

Exploitarium appeared during a period when AI-generated security vulnerabilities had been “flooding the bug bounty programs of many manufacturers,” contributing to what some described as a “Vulnocalypse.” The cURL project responded by declaring a “Summer of Bliss” in which it would not process bug reports during July.<\/cite><\/p>\n

This context matters. Exploitarium was not an isolated phenomenon but part of a broader shift in how vulnerabilities are discovered, disclosed, and weaponized. The automation of fuzzing, the use of large language models to generate proof-of-concept code, and the reduction in skill required to produce working exploits have all lowered the barrier to entry for vulnerability research. That democratization has benefits, but it also introduces noise, volume, and ethical ambiguity into disclosure ecosystems that were already strained.<\/p>\n

The result is an environment in which maintainers of open-source projects, already under-resourced and operating on volunteer time, face an accelerating volume of reports of varying quality, some legitimate, some spurious, and some weaponized before the maintainer even reads the email. The social contract that underpinned coordinated disclosure assumed good faith and finite volume. Both assumptions are now under stress.<\/p>\n

What Happened Next<\/h2>\n

The exploitarium repository was removed by GitHub within days of publication.<\/cite> However, the content persists in mirrors, and attackers are now using AI to scan for vulnerable instances.<\/cite> In many cases, the published proof-of-concept code meant attackers did not even have to spend time developing an exploit.<\/cite><\/p>\n

The removal of the repository did not eliminate the risk. Mirrors exist. The vulnerabilities remain in deployed software until patches are applied. The operational question for administrators is not whether exploitarium still exists on GitHub, but whether their infrastructure is running any of the affected software, whether patches are available, and whether those patches have been tested and deployed.<\/p>\n

Organizations running email infrastructure should treat any mention of libraries like libssh2, OpenVPN, or Gitea in their stack as a prompt to verify versions, consult CVE databases, and prioritize updates. The specific exploits published in June 2026 will eventually age out of relevance, but the pattern will repeat. The next repository might have a different name, a different author, and a different set of targets, but the operational response remains the same: identify exposure, test patches, deploy quickly.<\/p>\n","protected":false},"excerpt":{"rendered":"

Exploitarium is a GitHub repository that published proof-of-concept exploits for previously undisclosed vulnerabilities across multiple open-source projects, sparking debate about disclosure ethics and weaponizing security research.<\/p>\n","protected":false},"author":1,"featured_media":256,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12],"tags":[364,365,362,361,358,290,288,363,360,294,359],"class_list":["post-257","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-email-security","tag-bug-bounty-ethics","tag-coordinated-disclosure","tag-cve","tag-email-infrastructure-security","tag-exploitarium","tag-github-security","tag-libssh2","tag-open-source-security","tag-responsible-disclosure","tag-vulnerability-disclosure","tag-zero-day-vulnerabilities"],"yoast_head":"\nWhat Is Exploitarium? Understanding the Zero-Day Repository - Onion Mail \u2014 Privacy, Encryption & Tor<\/title>\n<meta name=\"description\" content=\"Exploitarium is a GitHub repository of zero-day exploits published without vendor disclosure in June 2026. Learn what it contains, how it differs from responsible disclosure, and what it means for email security.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"What Is Exploitarium? Understanding the Zero-Day Repository - Onion Mail \u2014 Privacy, Encryption & Tor\" \/>\n<meta property=\"og:description\" content=\"Exploitarium is a GitHub repository of zero-day exploits published without vendor disclosure in June 2026. Learn what it contains, how it differs from responsible disclosure, and what it means for email security.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/\" \/>\n<meta property=\"og:site_name\" content=\"Onion Mail \u2014 Privacy, Encryption & Tor\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-10T07:05:31+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/onionmail.org\/wp-content\/uploads\/2026\/08\/exploitarium-20260810.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"800\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Onion Mail\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Onion Mail\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/what-is-exploitarium-zero-day-repository-explained\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/what-is-exploitarium-zero-day-repository-explained\\\/\"},\"author\":{\"name\":\"Onion Mail\",\"@id\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/#\\\/schema\\\/person\\\/165910c3149db6a9320ddae7d7a17cab\"},\"headline\":\"What Is Exploitarium? Understanding the Zero-Day Repository\",\"datePublished\":\"2026-08-10T07:05:31+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/what-is-exploitarium-zero-day-repository-explained\\\/\"},\"wordCount\":1407,\"image\":{\"@id\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/what-is-exploitarium-zero-day-repository-explained\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/onionmail.org\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/exploitarium-20260810.jpg\",\"keywords\":[\"bug bounty ethics\",\"coordinated disclosure\",\"CVE\",\"email infrastructure security\",\"exploitarium\",\"GitHub security\",\"libssh2\",\"open-source security\",\"responsible disclosure\",\"vulnerability disclosure\",\"zero-day vulnerabilities\"],\"articleSection\":[\"Email Security\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/what-is-exploitarium-zero-day-repository-explained\\\/\",\"url\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/what-is-exploitarium-zero-day-repository-explained\\\/\",\"name\":\"What Is Exploitarium? Understanding the Zero-Day Repository - Onion Mail \u2014 Privacy, Encryption & Tor\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/what-is-exploitarium-zero-day-repository-explained\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/what-is-exploitarium-zero-day-repository-explained\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/onionmail.org\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/exploitarium-20260810.jpg\",\"datePublished\":\"2026-08-10T07:05:31+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/#\\\/schema\\\/person\\\/165910c3149db6a9320ddae7d7a17cab\"},\"description\":\"Exploitarium is a GitHub repository of zero-day exploits published without vendor disclosure in June 2026. Learn what it contains, how it differs from responsible disclosure, and what it means for email security.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/what-is-exploitarium-zero-day-repository-explained\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/onionmail.org\\\/blog\\\/what-is-exploitarium-zero-day-repository-explained\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/what-is-exploitarium-zero-day-repository-explained\\\/#primaryimage\",\"url\":\"https:\\\/\\\/onionmail.org\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/exploitarium-20260810.jpg\",\"contentUrl\":\"https:\\\/\\\/onionmail.org\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/exploitarium-20260810.jpg\",\"width\":1200,\"height\":800,\"caption\":\"exploitarium - red padlock on black computer keyboard\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/what-is-exploitarium-zero-day-repository-explained\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"What Is Exploitarium? Understanding the Zero-Day Repository\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/\",\"name\":\"Onion Mail \u2014 Privacy, Encryption & Tor\",\"description\":\"Anonymous email, PGP encryption and post-quantum security guides\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/#\\\/schema\\\/person\\\/165910c3149db6a9320ddae7d7a17cab\",\"name\":\"Onion Mail\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f7d6948c15418aed2d5fc684c551bb93fe70d354338e034960230227dad93ec9?s=96&d=initials&r=g&initials=in\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f7d6948c15418aed2d5fc684c551bb93fe70d354338e034960230227dad93ec9?s=96&d=initials&r=g&initials=in\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f7d6948c15418aed2d5fc684c551bb93fe70d354338e034960230227dad93ec9?s=96&d=initials&r=g&initials=in\",\"caption\":\"Onion Mail\"},\"sameAs\":[\"https:\\\/\\\/onionmail.org\"],\"url\":\"https:\\\/\\\/onionmail.org\\\/blog\\\/author\\\/adminblogonion\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"What Is Exploitarium? Understanding the Zero-Day Repository - Onion Mail \u2014 Privacy, Encryption & Tor","description":"Exploitarium is a GitHub repository of zero-day exploits published without vendor disclosure in June 2026. Learn what it contains, how it differs from responsible disclosure, and what it means for email security.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/","og_locale":"en_US","og_type":"article","og_title":"What Is Exploitarium? Understanding the Zero-Day Repository - Onion Mail \u2014 Privacy, Encryption & Tor","og_description":"Exploitarium is a GitHub repository of zero-day exploits published without vendor disclosure in June 2026. Learn what it contains, how it differs from responsible disclosure, and what it means for email security.","og_url":"https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/","og_site_name":"Onion Mail \u2014 Privacy, Encryption & Tor","article_published_time":"2026-08-10T07:05:31+00:00","og_image":[{"width":1200,"height":800,"url":"https:\/\/onionmail.org\/wp-content\/uploads\/2026\/08\/exploitarium-20260810.jpg","type":"image\/jpeg"}],"author":"Onion Mail","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Onion Mail","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/#article","isPartOf":{"@id":"https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/"},"author":{"name":"Onion Mail","@id":"https:\/\/onionmail.org\/blog\/#\/schema\/person\/165910c3149db6a9320ddae7d7a17cab"},"headline":"What Is Exploitarium? Understanding the Zero-Day Repository","datePublished":"2026-08-10T07:05:31+00:00","mainEntityOfPage":{"@id":"https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/"},"wordCount":1407,"image":{"@id":"https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/#primaryimage"},"thumbnailUrl":"https:\/\/onionmail.org\/wp-content\/uploads\/2026\/08\/exploitarium-20260810.jpg","keywords":["bug bounty ethics","coordinated disclosure","CVE","email infrastructure security","exploitarium","GitHub security","libssh2","open-source security","responsible disclosure","vulnerability disclosure","zero-day vulnerabilities"],"articleSection":["Email Security"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/","url":"https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/","name":"What Is Exploitarium? Understanding the Zero-Day Repository - Onion Mail \u2014 Privacy, Encryption & Tor","isPartOf":{"@id":"https:\/\/onionmail.org\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/#primaryimage"},"image":{"@id":"https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/#primaryimage"},"thumbnailUrl":"https:\/\/onionmail.org\/wp-content\/uploads\/2026\/08\/exploitarium-20260810.jpg","datePublished":"2026-08-10T07:05:31+00:00","author":{"@id":"https:\/\/onionmail.org\/blog\/#\/schema\/person\/165910c3149db6a9320ddae7d7a17cab"},"description":"Exploitarium is a GitHub repository of zero-day exploits published without vendor disclosure in June 2026. Learn what it contains, how it differs from responsible disclosure, and what it means for email security.","breadcrumb":{"@id":"https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/#primaryimage","url":"https:\/\/onionmail.org\/wp-content\/uploads\/2026\/08\/exploitarium-20260810.jpg","contentUrl":"https:\/\/onionmail.org\/wp-content\/uploads\/2026\/08\/exploitarium-20260810.jpg","width":1200,"height":800,"caption":"exploitarium - red padlock on black computer keyboard"},{"@type":"BreadcrumbList","@id":"https:\/\/onionmail.org\/blog\/what-is-exploitarium-zero-day-repository-explained\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/onionmail.org\/blog\/"},{"@type":"ListItem","position":2,"name":"What Is Exploitarium? Understanding the Zero-Day Repository"}]},{"@type":"WebSite","@id":"https:\/\/onionmail.org\/blog\/#website","url":"https:\/\/onionmail.org\/blog\/","name":"Onion Mail \u2014 Privacy, Encryption & Tor","description":"Anonymous email, PGP encryption and post-quantum security guides","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/onionmail.org\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/onionmail.org\/blog\/#\/schema\/person\/165910c3149db6a9320ddae7d7a17cab","name":"Onion Mail","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/f7d6948c15418aed2d5fc684c551bb93fe70d354338e034960230227dad93ec9?s=96&d=initials&r=g&initials=in","url":"https:\/\/secure.gravatar.com\/avatar\/f7d6948c15418aed2d5fc684c551bb93fe70d354338e034960230227dad93ec9?s=96&d=initials&r=g&initials=in","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f7d6948c15418aed2d5fc684c551bb93fe70d354338e034960230227dad93ec9?s=96&d=initials&r=g&initials=in","caption":"Onion Mail"},"sameAs":["https:\/\/onionmail.org"],"url":"https:\/\/onionmail.org\/blog\/author\/adminblogonion\/"}]}},"_links":{"self":[{"href":"https:\/\/onionmail.org\/blog\/wp-json\/wp\/v2\/posts\/257","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/onionmail.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/onionmail.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/onionmail.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/onionmail.org\/blog\/wp-json\/wp\/v2\/comments?post=257"}],"version-history":[{"count":0,"href":"https:\/\/onionmail.org\/blog\/wp-json\/wp\/v2\/posts\/257\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/onionmail.org\/blog\/wp-json\/wp\/v2\/media\/256"}],"wp:attachment":[{"href":"https:\/\/onionmail.org\/blog\/wp-json\/wp\/v2\/media?parent=257"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/onionmail.org\/blog\/wp-json\/wp\/v2\/categories?post=257"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/onionmail.org\/blog\/wp-json\/wp\/v2\/tags?post=257"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}