Skip to content

Peptide COA watchdog · Evidence-led case files · Corrections welcomed

The COA Catcher home

The COA Catcher

Evidence has a trail. We follow it.

Documented case record

Defcon Peptides

Published or last materially updated:

Case scope matters. This record concerns the product, batch, transaction, or evidence identified in the article. It should not be read as a finding about every product sold by a vendor, or as proof of intent or illegality. Review the source material, limitations, status, and any response together.

Case evidence details

Evidence published Suspected document or authentication issue

The publisher has posted sources concerning the specific product or batch described. Readers should assess the cited material and any vendor response.

Cited material raises a document-authenticity or provenance concern; it is not an official finding unless separately stated.

Vendor URL (reference only)
defconpeptides.com.au
Seller identity at the time
Defcon Peptides
Product / batch scope
Six COA entries displayed on the Defcon Peptides Certificates of Analysis page on 31 August 2026; specifically report identifiers KVR-2026-2A0656 and KVR-2026-56F742 for the attribution comparison.
Batch / lot / order ID
Report identifiers KVR-2026-2A0656 and KVR-2026-56F742

Chain of custody and provenance

Public-document review. The supplier’s public COA summaries were compared with the provider-hosted Kovera Labs PDF for KVR-2026-2A0656, an indexed record for the same report, and public report indexes. No physical sample was obtained or tested, so sample custody is not applicable. The public record did not demonstrate how the referenced Ion Peptide batches connected to Defcon inventory.

Evidence summary

Six public “View Full COA” entries opened seller-created summaries without original Janoshik task numbers, unique keys or direct verification links. Two displayed KVR report identifiers matched Kovera Labs / Ion Peptide records, creating a laboratory-attribution discrepancy. This finding is limited to document attribution and public verification; it does not establish product identity, purity, quantity, sterility or safety.

Sources and references

  1. https://thecoacatcher.com/six-janoshik-coas-zero-janoshik-links/
  2. https://defconpeptides.com.au/certificates-of-analysis/
  3. https://abr.business.gov.au/ABN/View?id=53197018912
  4. https://janoshik.com/verification/
  5. https://peptidebenchmark.com/testing/coas/2496ddfd0f214f7287a3/
  6. https://ldannhtclefopuppzhyz.supabase.co/storage/v1/object/public/coa-files/d/640286bffdccbf42/r.pdf
  7. https://www.disclosedlabs.com/labs/kovera-labs

Laboratory test details

Laboratory
Kovera Labs (matching source report); Janoshik attribution claimed on supplier summaries
Method
Document attribution and source cross-check; no laboratory testing performed by The COA Catcher

Result as reported

Two displayed KVR identifiers were associated with Kovera Labs / Ion Peptide records rather than a publicly verifiable Janoshik certificate. No original Janoshik task number, unique key or direct verification link was found in the six summaries reviewed.

Vendor response

No vendor response has been recorded.

Limitations and uncertainty

This is a public-document attribution review, not a chemical or sterility test. No physical sample or seller-to-source chain of custody was established. The records do not prove the products counterfeit, contaminated, under-dosed or unsafe, and do not prove that a private Janoshik report does not exist. The status may change if original reports, verification keys or inventory linkage are supplied.

Editorial review record

Public change log

31 August 2026 — Initial evidence record prepared; proposed status Evidence published / Suspected document or authentication issue; right of reply open.

Scope note: this record concerns only the cited product, batch, transaction, and source material. It is not a blanket judgment about every product or activity of the named vendor, and it is not a legal determination.

Absence from this directory is not evidence that a vendor or product is safe, genuine, lawful, or suitable.

Reading this record

Evidence: Open the cited material where available; a summary is not a substitute for the source.

Status: Check whether the case is under review, published with limitations, corrected, or closed.

Response: Vendor context and disputes should be clearly labelled and presented with the record.

Updates: Material changes should be dated in the correction history.

Read the methodology

Correction or right of reply

If you are named or materially affected by this record, you can challenge an error, add context, or provide an on-record response. Material corrections are dated and remain visible.

Review the right-of-reply process