Gardyn Security Incident

Archive Captures

Independent captures of Gardyn-published URLs referenced in CISA advisory ICSA-26-055-03 and on this site. SHA-256 hashes establish chain-of-custody.

Manifest

The full manifest is at /captures/manifest.json. It records, for each URL: timestamp of fetch, HTTP response chain (including any redirects), final URL, byte size, SHA-256 hash, and JSON-LD dateModified / datePublished values where present.

Captures (April 27, 2026, 04:59:38 UTC)

https://mygardyn.com/blog/security-update/

HTTP response200 OK
Bytes818,317
SHA-256f55aea5b9705b71792382d86d0dc0da7515b2084eb464a1027965598ab20bf48
JSON-LD datePublished2026-02-24T18:38:01+00:00
JSON-LD dateModified2026-04-07T18:05:17+00:00
Local capturemygardyn.com_blog_security-update.html

https://mygardyn.com/policy/privacy/

HTTP response200 OK
Bytes883,098
SHA-256ed17b9143db5e3547f6e08ea306a67e3c5272d814c10d366eb0fc1d3dc06e614
JSON-LD datePublished2019-05-08T01:38:14+00:00
JSON-LD dateModified2026-03-20T12:36:12+00:00
Local capturemygardyn.com_policy_privacy.html

https://mygardyn.com/security/

HTTP response chain301 Moved Permanently → 200 OK
Final URLhttps://mygardyn.com/blog/security-update/
Bytes (after redirect)818,317
SHA-256 (after redirect)2f17c5ce577fea699bef42a20fd7f9d11e274ed432703f864aabd52ab031e881
JSON-LD datePublished2026-02-24T18:38:01+00:00
JSON-LD dateModified2026-04-07T18:05:17+00:00
Local capturemygardyn.com_security.html

Wayback Machine

Wayback Machine programmatic submission requires Internet Archive S3-style API credentials. The maintainer is performing Wayback submission interactively and will append the resulting Wayback snapshot URLs to manifest.json as they become available. Independent third-party Wayback submissions of these URLs are welcomed and can be triggered by anyone at web.archive.org/save/.

Independently verifying these captures

To verify a SHA-256 hash from the manifest:

curl -sL "https://mygardyn.com/blog/security-update/" -A "Mozilla/5.0" | shasum -a 256

The hash will not match exactly because the page contains dynamic elements (e.g., a marketing countdown timer); however, the editorial content (the article body, FAQ section, and JSON-LD metadata) is stable. The local capture file in this directory preserves the byte-for-byte content as fetched at the timestamp recorded in the manifest.

Chain of custody

All captures were fetched via curl 8.x with User-Agent Mozilla/5.0 (Macintosh; Intel Mac OS X) gardyn-security-incident-docs/1.0 from the maintainer's workstation in Fort Lee, NJ, USA, on April 27, 2026 at 04:59:38 UTC. No content was modified between fetch and storage. SHA-256 hashes were computed via shasum -a 256 on the as-fetched bytes.