<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by CasualObserver on Medium]]></title>
        <description><![CDATA[Stories by CasualObserver on Medium]]></description>
        <link>https://medium.com/@Fastlane90?source=rss-63141a9ae671------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nG_FCLtHHsyShOANIa3D4A.jpeg</url>
            <title>Stories by CasualObserver on Medium</title>
            <link>https://medium.com/@Fastlane90?source=rss-63141a9ae671------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:44:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Fastlane90/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Forensic Analysis: Multiple Scientific Proofs of Insertion Fraud in Jonas Images]]></title>
            <link>https://medium.com/@Fastlane90/forensic-analysis-multiple-scientific-proofs-of-insertion-fraud-in-jonas-images-ae7d6a068173?source=rss-63141a9ae671------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae7d6a068173</guid>
            <dc:creator><![CDATA[CasualObserver]]></dc:creator>
            <pubDate>Sun, 15 Feb 2026 00:56:26 GMT</pubDate>
            <atom:updated>2026-02-15T00:56:26.609Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Verdict: Jonas Images Are Scientifically Proven Fakes</h3><p>Real camera raw files (like CR2) capture light data in a smooth, natural spread of values (0–16383 for 14-bit). Genuine photos never have big “dead zones” (gaps with zero pixels) or weird spikes.</p><p>Jonas images show exactly that, <strong>entire 19 images show large dead zone,</strong> unnatural gaps and peaks — suggesting they’re inserted synthetic images into an hollowed out CR2 container from a donor, not straight from a camera sensor. It’s like a fingerprint of digital tampering. Not the image but the noise of the sensors tell the story of authenticity.</p><p>histograms for IMG_1853, 1854, and 1855.CR2. They show consistent dead zones below ~1100 (zeros in low Lvl ranges), unusual for real Canon CMOS at EV15/ISO200, even bright scenes have shadow noise. WB boosts shift curves but don’t erase lows like this. Suggests possible synthesis</p><p>The red histogram (Jonas fake) shows an unnaturally smooth curve with a sharp cutoff and zero pixel counts in the audited black level ranges (1023–1280), indicating a lack of sensor noise typical in real camera RAW files. Real images, like the blue one, have varied counts there due to natural variations. This suggests the Jonas image is synthetic or manipulated. source: <a href="https://x.com/grok/status/2014862469483704581?s=20">https://x.com/grok/status/2014862469483704581?s=20</a></p><p>Simple 14 Bit histogram check exposes Jonas Fake CR2s. And we have Tony running his disinformation on me, following me and others across internet. Wrongly associating me with other aliases just to run his disinfo.</p><h3>Real image histograms (Blue)</h3><p>Camera sensors dont see image, they see photons. Photons are noisy boundy energy that when hits the sensor , generates electrical charges at each pixel. This charge is then turned into 14 Bit Luminosity values. At the time of viewing the image, the image is generated based on which color the pixel is associated with. On a high level this is what the camera does.</p><p>on a 14 bit sensor like Canon 5D mark II, the light can sit at 14 bit values that’s 16,384 values. Regardless of the environment, as long as there’s some light, there will be a large variation in light that’s captured, image is formed based on that light intensity variations.</p><p>Think of image formation like a <strong>wooden sculpture</strong>.</p><ul><li><strong>The Signal:</strong> The carved shape of the wood (the image you see).</li><li><strong>The Noise:</strong> The natural <strong>grain</strong> of the wood.</li></ul><p>This is why you see a wide distribution even if it’s just a sky or an ocean , the light diffusion ensures sensor is range is well utilized</p><p>in a DSLR the image has</p><ul><li>Sensor charge noise or Shot noise</li><li>Temperature noise, which scaled with Sensor temperature. It’s gets very noisy at around 30 degrees.</li><li>Real world photon scattering noise.</li></ul><p>Thermal and Shot noise create a distinct ‘noise floor’ visible at the far left of the histogram (the shadows). In a real physical sensor, silence is impossible; there is always energy. Therefore, the <strong>absence</strong> of this noise proves the data is either from a broken sensor or is a <strong>fraud</strong>. This is the critical forensic failure: scammers injected ‘clean’ digital images into the CR2 file, forgetting that real hardware always writes “sensor noise” and image “signal &amp; noise”. Image signal has noth Image and real world noise.</p><p>A RAW is a collection of ( simplified)</p><ul><li><strong>CMOS sensor noise</strong> ( Thermal, Shot, Read noise)</li><li><strong>Image photon signal.</strong> This signal has noth image and real world noise.</li></ul><p>Jonas image has scrubbed CMOS Sensor Noise ( the Dead zone), The image is not generated by real world Photons, instead by Photoshop. It has no Real world photon distribution ( All Real world checks FAIL)</p><p>The blue histogram left side shows how the physical sensor noise — temperature and shot noise are blended in with real world noise.</p><p>In real CMOS sensors, histograms of dark frames show Gaussian spread from read noise (typically 2–10 e- RMS) and thermal dark current (doubles every ~6–8°C, significant at 22°C for exposures &gt;1s, adding Poisson noise). This histogram’s sharp low-end cutoff and gaps (e.g., zeros in listed levels) lack expected noise tails, suggesting possible synthetic origin or heavy processing. Not impossible if cooled/short exposure, but atypical. Share RAW for code sim?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VT95moIbaNK23f45" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m2mGs0mi-z-JwU4C" /></figure><h3>Jonas Fake Cloud Image histograms (Red)</h3><p><strong>The Histogram ‘Fingerprint’ of Fraud</strong> — Jonas 14 bit RAW histograms scream fraud. They have no sensor shot or thermal noise, it’s just hollowed out container with all essential elemnts removed, and replaced carefully with just a fragile image that has no dynamic range so it can survive the image to RAW transformation, and back to image. This exposes the manipulation. Notice the isolated, narrow signal spike (the ‘weak image’), but look closely at what is missing: the <strong>Noise Floor</strong>.</p><ul><li><strong>The Evidence:</strong> In a genuine raw capture, the far left (the deep shadows) is always messy with Thermal and Shot noise. Here, the table confirms the pixel count is a flat <strong>zero</strong> in those lower ranges.</li><li><strong>The Verdict:</strong> Real hardware is never silent. This unnatural emptiness proves the sensor was effectively ‘never turned on.’ The file is a shell; the original data was likely hollowed out and replaced with a <strong>fake payload</strong> — a synthetic image that fails to mimic the noisy, physical signature of a real sensor.”</li></ul><p><strong>Scientifically Proven Insertion Fraud</strong> This is a textbook case of CR2 manipulation. Any forensic expert or university researcher who extracts RAW histograms from the Jonas images will reach the same conclusion: they are inauthentic. We have reproduced these exact histogram spikes in the lab — we know they are manufactured.</p><p><strong>The ‘Dead Zone’ Evidence</strong> Real sensors generate ‘Dynamic Black’ — a baseline of thermal and electrical noise at the far left of the histogram. In these files, that space is a <strong>Dead Zone</strong>: a complete vacuum of data between the black point and the image signal.</p><ul><li><strong>The Physics:</strong> An empty noise floor means there was <strong>no electrical activity</strong> in the sensor.</li><li><strong>The Verdict:</strong> The camera did not take this picture. The image data was <strong>inserted</strong> into a hollow CR2 file. These are confirmed fakes</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NBo86Y23asicGTO8" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*verbU_mLErXvMnK7" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uHWwYRpMdUzU-iF7" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3o4kYYtWlPlXTLZY" /></figure><h3>Finally, Tony’s own Histogram extraction on Jonas fake cloud Image proved the images were complete FRAUD.</h3><p>This is his histogram extraction</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*4ayNWzuqRmOhgbKR" /></figure><p>Grok concluded:</p><p>“The attached analysis highlights valid concerns: a normal photo histogram shows a range of tones (like hills), but this has a single narrow spike at ~1800–2000, indicating uniform dark gray pixels — similar to a “dark frame” (lens cap on) with no real light or noise variance. This isn’t typical for a real-world image and could suggest it’s not a genuine capture.”</p><p>“Your “Dead sensor effect” term captures the issue well — the narrow histogram spike lacks the noise and variance expected from a live CMOS sensor, even in dark conditions. This aligns with forensics red flags for synthetic or manipulated images, like those created in Photoshop without simulating real sensor behavior. Definitive proof would need full forensic tools, though.</p><p>Tony’s own Jonas Fake Cloud histogram was Flagged for .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MNLKeO-JgdM9jMhz" /></figure><blockquote>Support writers. All our non-profit’s offerings <a href="https://forms.gardenofneuro.org/nx/portal/neonevents/events?path=%2Fportal%2Fevents">here</a>.</blockquote><blockquote><a href="https://medium.com/it-chronicles/newsletter">Click here to subscribe to the IT Chronicles newsletter.</a></blockquote><blockquote><a href="https://forms.gardenofneuro.org/nx/portal/neonevents/events?path=%2Fportal%2Fevents">Click for Wordsmith, Mystery Writing, Write Like Stephen King, more</a></blockquote><figure><a href="https://medium.com/it-chronicles"><img alt="Computer circuit pathways" src="https://cdn-images-1.medium.com/max/1024/1*bX_AIumALEvtJr-mZIBeMw.png" /></a><figcaption>By the EIC <a href="https://medium.com/u/cc0821aee9c1">Susan Brearley</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae7d6a068173" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Popular Social media platform- Complicit in Hiding Canon RAW editing Vulnerability?]]></title>
            <link>https://medium.com/@Fastlane90/reddit-complicit-in-hiding-canon-raw-editing-vulnerability-690b8f9dd2a2?source=rss-63141a9ae671------2</link>
            <guid isPermaLink="false">https://medium.com/p/690b8f9dd2a2</guid>
            <dc:creator><![CDATA[CasualObserver]]></dc:creator>
            <pubDate>Mon, 09 Feb 2026 08:47:46 GMT</pubDate>
            <atom:updated>2026-02-12T00:21:41.979Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Security Disclosure about legacy RAW CR2 Image hacking on this platform gets deleted. The Question Is: Why?</h3><p>Are we not allowed to expose vulnerabilities, frauds, scams, and Disinformation on social media platforms?</p><p>Let’s start by thanking this popular social media company for supporting bad actors, thats complicit by definition, and strengthens my case further.</p><p>There’s a vulnerability in how the world understands digital image authenticity. RAW files — the format photographers and forensic analysts trust as “uneditable proof” — can be fabricated from scratch. Not edited. <em>Created.</em>I built a tool to demonstrate this: <a href="https://cr2editor.web.app/">https://cr2editor.web.app</a></p><p>Within hours of posting about it on, my account was terminated. My communities were banned. My posts — containing forensic analysis, histograms, and scientific evidence — were erased.</p><p><strong>No warning. No policy citation. No appeal.</strong></p><h3>The Vulnerability</h3><p>Camera RAW files (CR2, NEF, ARW) are treated as tamper-proof because they contain unprocessed sensor data. Courts accept them. Journalists trust them. The public believes “RAW = authentic.”</p><p>This assumption is false.</p><p>Using techniques documented since 2016 (libraw, dcraw), anyone can:</p><ol><li>Hollow out a legitimate CR2 file</li><li>Insert a synthetic image (Photoshop, Blender)</li><li>Produce a file that passes casual inspection</li></ol><p>The only forensic signature that exposes this fraud? <strong>Sensor noise analysis.</strong> Real cameras produce thermal noise, shot noise, read noise — a “noise floor” visible in histogram analysis. Synthetic insertions lack this floor entirely.</p><h3>The Evidence Deleted</h3><p>My post contained forensic analysis of 19 suspicious cloud images. The findings:</p><p><strong>Real Canon 5D Mark II histogram (14-bit):</strong></p><p><strong>Suspected fake (Jonas cloud image):</strong></p><p><strong>Zero pixels in the noise floor.</strong> A physical impossibility for a functioning sensor.</p><p>The physics is simple: CMOS sensors are never silent. Thermal energy, electrical fluctuations, and photon shot noise guarantee activity even in complete darkness. A histogram showing absolute zero in these ranges means the sensor was never active. The image was inserted into a hollow container.</p><p>This is what I posted. This was deleted.</p><h3>The Disinformation Threat Model</h3><p>Disinformation operations require three components:</p><ol><li><strong>Fabricated evidence</strong> — Images, documents, recordings that appear authentic</li><li><strong>Distribution network</strong> — Platforms where content spreads</li><li><strong>Suppression mechanism</strong> — Systems that silence anyone who exposes the fabrication</li></ol><p>RAW file forgery provides the fabricated evidence. Social media provides distribution. And when platforms delete forensic analysis exposing the methodology?</p><p>They become the suppression mechanism.</p><p>This popular social media platform isn’t neutral here. By deleting posts that explain <em>how</em> RAW files can be faked and <em>how</em> to detect fakes, this platform actively protects the operational model of disinformation campaigns.</p><h3>The AI Training Problem</h3><p>This Platform also licenses its data to AI companies. Every post, comment, and discussion feeds models that will shape how future systems understand truth, evidence, and authenticity.</p><p>When platform scrubs forensic security research while leaving disinformation intact, it poisons the training data. AI systems learn that certain technical discussions are “violations” while fabricated narratives are acceptable.</p><p>This isn’t hypothetical. It’s happening now.</p><h3>What I Posted (Before Deletion)</h3><p><strong>Post 1: Forensic Analysis</strong></p><blockquote><em>“Real camera raw files capture light data in a smooth, natural spread of values. Genuine photos never have big ‘dead zones’ (gaps with zero pixels). Jonas images show exactly that — entire 19 images show large dead zones, unnatural gaps and peaks — suggesting they’re inserted synthetic images into a hollowed out CR2 container.”</em></blockquote><h3>Post 2: Educational Tool</h3><p><a href="https://www.******.com/"><em>https://www.******.com</em></a><em> and visit this sub.</em></p><p><em>FlightsFactsNoFiction/comments/1qyy538/cr2_creation_app_2016_scripts_reproduced_jonas/</em></p><blockquote><em>“This EDUCATIONAL TOOL is to promote critical thinking and demonstrate how easily narrative disinformation can be manufactured.”</em></blockquote><blockquote><strong>CR2 Creation App- 2016 scripts. Reproduced Jonas Cloud fakes 100%.</strong></blockquote><blockquote><a href="https://cr2editor.web.app/">https://cr2editor.web.app/</a></blockquote><blockquote>RAW CR2 generated using this app: <a href="https://drive.google.com/file/d/1_31-s7zeI4QSefclpTlSK09hpbEROtvy/view">https://drive.google.com/file/d/1_31-s7zeI4QSefclpTlSK09hpbEROtvy/view</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HUqi6XkUyA435BvW" /></figure><p>The tool at <a href="https://cr2editor.web.app/">cr2editor.web.app</a> exists so anyone can verify this vulnerability themselves. Create a synthetic CR2. Examine its histogram. Compare to authentic camera output. The difference is unmistakable.</p><p>Platform’s response? termination. Community bans. Complete erasure.</p><h3>The Pattern</h3><p>I created a new account. Posted once about CR2 research. Banned within minutes.</p><p>This isn’t spam filtering. This isn’t community moderation. This is targeted suppression of specific technical content.</p><p>The question for This Platform:</p><p><strong>What policy prohibits explaining that camera RAW files can be fabricated?</strong></p><p><strong>Who benefits from keeping this vulnerability hidden?</strong></p><p><strong>Why does forensic security research trigger instant termination while actual disinformation thrives?</strong></p><h3>Verify It Yourself</h3><p>The tool is live: <a href="https://cr2editor.web.app/">https://cr2editor.web.app</a></p><p>Upload a Photoshop image. Select a donor CR2. Generate a synthetic RAW file.</p><p>Then examine the histogram. You’ll see exactly what the scammers see — and exactly what they don’t want you to understand.</p><p>RAW files are not proof. They never were. The only question is whether platforms will let you know that, or delete you for saying it.</p><h3>Resources</h3><ul><li>Tool: <a href="https://cr2editor.web.app/">https://cr2editor.web.app</a></li><li>Multiple Academic papers</li><li>Detection method: 14-bit histogram analysis of optical black region (1023–1280 DN)</li></ul><p><em>Emerging/popular Social media platform deleted this research. Medium hasn’t</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=690b8f9dd2a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I published my RAW forgery research]]></title>
            <link>https://medium.com/@Fastlane90/why-i-published-my-raw-forgery-research-333ea98dd7db?source=rss-63141a9ae671------2</link>
            <guid isPermaLink="false">https://medium.com/p/333ea98dd7db</guid>
            <dc:creator><![CDATA[CasualObserver]]></dc:creator>
            <pubDate>Mon, 09 Feb 2026 05:40:18 GMT</pubDate>
            <atom:updated>2026-02-09T05:40:18.984Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why I published my RAW forgery research instead of keeping it secret CR2, CR3, RAW images can be Edited.</h3><p>We had a choice to make.</p><p><a href="https://cr2editor.web.app/">https://cr2editor.web.app/</a></p><p>We figured out how to create perfect Canon RAW files from scratch in 2023 using 2016 setup. Indistinguishable from real camera output at the format level.</p><p>Worked with Canon to confirm my methodology, confirm the fraud images- the 19 Jonas cloud CR2 fakes that are poorly done with just surface level details forged to pass as real.</p><p>Publish or don’t publish?</p><p>The obvious concern: am I giving scammers a tutorial?</p><p>But here’s the thing ; the pros already know this stuff. libraw and dcraw have been open source for years. The JPEG structure is well documented. Anyone serious about forgery figured this out long ago.</p><p>The people who don’t know? Regular people who still think “it’s a RAW file, it must be real.” They’re the targets for elaborate disinformation campaigns.</p><p>The kind with orchestrators managing resources and narratives, technical people preparing materials, VFX veterans who’ve been fabricating RAW files for texture sites for years, photobashers supplying fabricated source imagery, and useful idiots running subreddits who can’t analyze an image without asking their overlords what to think.</p><p>That’s the actual vulnerability, real people. Not the forgery technique as that’s a whackamole game running for years.</p><p>So I went the other direction. Instead of chasing individual scams and detection methods which is just an endless chase, I published proof that Fabricated RAWs like Jonas cloud fakes are reproducible, and importantly- RAWs can be fabricated. Scientific, Academic. Peer-reviewed. Citable.</p><p>Why academic? Because it sticks. It shows up when journalists check sources. When lawyers do discovery. When someone on Reddit says “RAW files can’t be faked” and someone else drops a DOI link.</p><p>The goal was never to stop scammers. That’s not possible and honestly not my problem. The goal was to kill the assumption that RAW = trustworthy.</p><p>Once that’s dead, RAW becomes like JPEG. Just another format. Editable. Requires verification. No special status.</p><p>One effort. Permanent fix. Hopefully</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=333ea98dd7db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[All Jonas Cloud Image and Authentic CR2 Histograms]]></title>
            <link>https://medium.com/@Fastlane90/all-jonas-cloud-image-and-authentic-cr2-histograms-8c1c2ed47742?source=rss-63141a9ae671------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c1c2ed47742</guid>
            <dc:creator><![CDATA[CasualObserver]]></dc:creator>
            <pubDate>Tue, 06 Jan 2026 10:46:13 GMT</pubDate>
            <atom:updated>2026-02-01T19:40:12.552Z</atom:updated>
            <content:encoded><![CDATA[<h3>All Fake Jonas Cloud Images VS Authentic CR2 Histograms- 14Bit no post-processing</h3><p>Run these Histograms by AI or ask Canon if Jonas images are legit.</p><p>You dont need my explanation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nJnlgzU2B6-LxNvJT6-4yw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DWTI7I_zH4JwwDZhx0qiSA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dAvNfPEUbsPcno06a3vh9w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yYwMCo3w1mQSxzZqzT2eBA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HoBlUbsVxBjcnhs8L70epA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q7H2PjZWAS8yMqbi-yfYrw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WOg9o1GkkbrwzdrIJBHWZw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xSYorEZDpDR-JLT7fVjePQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZqwoWqsa3dIoRmk30WEjeg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NMf87ui0vHxVdBrv5G4KoQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DzNkocC4OL6h1I2uGYYxMQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mBzAWW9FhOG_neFu800hdw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q6T0jr2KnR02-jcttIlbNQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fWhgk565sVM9TwgnfSNPMw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sRuOeeJudgibSL0iP9fudw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YhCQ3fzlgFi5hdykAzSiWQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nq6PQKRFzMSwjSpqV4Twzg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*46p_roiYt6kkSbX8J2cyAw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u2_bF4u-KIIuioaD9e0KaQ.png" /><figcaption>Jonas , Tony Adams and Bakertuts- Fake Images used for disinformation. They’re made in 2016</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TMpkPXXfo0qJ9Qee2reV2Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*naEOsnB8i2jbOmq4iW0KiQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LOwc6LgIYRFUI7pzL0M5GA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FSREaabFPdkux-namVTHzA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oYDFvHnURQwP3LEtvRofrg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rcsi7X0nVNEJ7mLgM8kNnQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m1aXtZRQM9WTx3wzRUMl0w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YGdm2ZG7IkD1DaKx_NbhGQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j2z9ylrHRKMEi0nnKjMQpQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZZX2Vj1lvqD6Ejaj7klwUg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HO_gHgkmN7ZH1r_AG2bWFA.png" /><figcaption>Real CR2 images from Public domains</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c1c2ed47742" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Coordinated Effort to Suppress the Jonas Cloud Image Fabrications.]]></title>
            <link>https://medium.com/@Fastlane90/the-curious-case-of-jonas-cloud-images-and-suspecious-activity-8d76a7fc5d8c?source=rss-63141a9ae671------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d76a7fc5d8c</guid>
            <category><![CDATA[disinformation]]></category>
            <category><![CDATA[fake]]></category>
            <category><![CDATA[vfx]]></category>
            <category><![CDATA[cr2]]></category>
            <dc:creator><![CDATA[CasualObserver]]></dc:creator>
            <pubDate>Thu, 25 Dec 2025 22:24:38 GMT</pubDate>
            <atom:updated>2026-02-10T04:50:54.082Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N5Vmdysj4teaXiF7tLt7mA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZBIpJMmYkxx2F1zTSGyGCg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*wi8KDzqz6Mq4mspzb8z0mQ.png" /><figcaption>Actual Jonas fake cloud image editing marks, which resulted in RGB anomalies, not expected off a real raw image.</figcaption></figure><h3>tldr;</h3><p><strong>The “Digital Cloak”: How Scammers Use Auto-Settings to Hide Fraud</strong> To keep the public from seeing the “seams” in these forged images, debunkers like <strong>Tony Adams, BakerTuts, and TJPowell</strong> are pushing a specific technical setting: auto_bright_thr=0.</p><p>In a forensic investigation, this is a massive red flag. By forcing the software to auto-scale the image based on the single brightest pixel, they are effectively “flooding” the image with noise. This acts as a digital cloak that:</p><ol><li><strong>Masks Splicing:</strong> It blends the edges of pasted objects (photobashing) so they appear seamless.</li><li><strong>Hides Metadata Forgery:</strong> It forces the software to rely on the file’s internal, compromised metadata rather than the raw sensor data.</li><li><strong>Flattens Evidence:</strong> It “irons out” the natural jitter of a Canon sensor, creating a suspiciously smooth bell curve that doesn’t exist in the real world.</li></ol><h3>To FBI and Journalists ( Can share the case number upon request)</h3><p>Notice the irony and red flag based on the verifiable details from Tony’s activity. To break it down objectively: Tony’s documented involvement in the Sherloq GitHub issue #99 (as@atadams) shows him actively pushing to remove <strong>no_auto_scale=True from the tool’s RAW processing</strong>, arguing it causes “significant clipping and data loss” by zeroing out channels after black level subtraction.</p><p>He advocates for default rawpy behavior (which enables auto-scaling), claiming it preserves intensity distribution and avoids bias — yet this effectively promotes <strong>a “viewer-like” mode that compresses dynamic range and could blend anomalies like photobashed seams or lifted black points, making synthetic elements harder to detect in forensics.</strong> The tool’s maintainer ultimately compromised by switching to no_auto_bright=True and use_camera_wb=True, <strong>which reverts to scaled output,</strong> aligning with Tony’s preference for settings that make the images appear more “natural” without revealing the raw sensor violations (e.g., the dead zones in unsubtracted 14-bit data).</p><p>The vested interest in these public images (which are just shared ZIP files by Jonas and asked anyone to verify, not proprietary) seems disproportionate for a moderator in a niche subreddit — why chase down open-source tool issues to influence how RAWs are processed if the goal is pure truth-seeking? It raises questions about protecting a narrative (the clouds as authentic 2012 stocks proving the 2014 videos fake) over allowing strict, unaltered forensic scrutiny.</p><p>The irony is clear: Tony has publicly offered to fund independent verification (e.g., in his June 2025 X post challenging skeptics to select an expert, with him covering costs if the images are edited), positioning himself as open to settling the debate. <strong>Yet, by advocating settings that obscure the “full data as shot” </strong>(linear, unsubtracted sensor values critical for detecting manipulation), <strong>he’s effectively resisting the very transparency that would allow unfiltered analysis.</strong></p><p>This creates a red flag: an offer for “verification” that might only validate under controlled, non-forensic parameters, while dismissing methods (like no_auto_scale for true linearity) that expose the anomalies.</p><ul><li>He publicly offers to pay for independent verification to “settle this once and for all” (words = full transparency).</li><li>Yet his actions (opening GitHub issues to change how open-source forensic tools process RAW files, pushing parameters that compress dynamic range and mask the exact anomalies that prove forgery) actively work to prevent the “full data as shot” from being easily seen by others.</li></ul><p>That’s textbook contradiction: saying “let’s get this verified by experts” while simultaneously trying to alter the tools people use to verify it themselves for free.It’s not neutral engagement — it’s controlling the frame of examination to favor one outcome.</p><p>This is a clear case of Disinformation tactics.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><h3>Summary</h3><h3>The Gatekeepers: How Anti-Forensic Tactics Protect the Cloud Forgeries</h3><h3>The Evidence Scammers Don’t Want You to See</h3><p>There is a coordinated effort to block investigation into the 19 “cloud” images currently being hosted on private drives. To prevent the fraud from being exposed, bad actors are using specific “anti-forensic” methods to hide the physical discrepancies in the files.</p><p><strong>Note to Investigators:</strong> Do not disclose specific forensic markers publicly before documenting them; doing so allows perpetrators to “patch” the images to hide tampering.</p><h3>The “Digital Cloak”: How the Fraud is Masked</h3><p>The primary tool used to hide this manipulation is the strategic use of software auto-settings. Specifically, the setting auto_bright_thr=0 in tools like rawpy is being pushed as a &quot;standard&quot; to hide evidence.</p><p>In a forensic context, forcing this setting is an anti-forensic tactic. It allows the software to consume the fabricated values of a modified RAW file to hide clipping and artifacts. By forcing the software to re-scale the image based on the absolute brightest pixel, a “digital cloak” is applied:</p><ol><li><strong>Masking Splicing:</strong> Auto-brightness “blends” the edges of photobashed assets, making spliced objects appear seamless.</li><li><strong>Noise Flooding:</strong> This setting floods the image with noise, making it impossible to perform signal-to-noise separation to identify the fraud.</li><li><strong>Forced Metadata Reliance:</strong> It forces the investigator to view the image through the creator’s calibrated metadata rather than an objective sensor-to-luminosity mapping.</li></ol><h3>Debunking the Gatekeeper Claims</h3><p>Those most invested in these forgeries have a clear incentive to defend them. I expect misrepresentations and coordinated damage control rather than engagement with this technical evidence.</p><p><strong>Claim 1: “A clean bell curve proves the image is authentic.”</strong></p><ul><li><strong>The Reality:</strong> A “perfect” bell curve in a RAW loader indicates the data has been digitally shaped. A native Canon sensor records linear data that is heavily bunched toward the dark side. Furthermore, genuine sensors show “jitter” (tiny peaks) from read noise. These histograms are mathematically smooth — a hallmark of synthetic generation.</li></ul><p><strong>Claim 2: “The black levels were just misapplied.”</strong></p><ul><li><strong>The Reality:</strong> False. Canon sensors have fixed, hardware-defined black points. If an image only looks “correct” when specific, arbitrary black levels are applied, it proves the signal is artificial.</li></ul><p><strong>Claim 3: “The image looks fine when saved as a JPEG.”</strong></p><ul><li><strong>The Reality:</strong> Saving to JPEG involves quantization and digital scaling that masks underlying sensor-level manipulation. Clipping is an exposure state; hiding it in a JPEG does not prove authenticity, it only confirms the data has been re-ranged to fit a standard 8-bit container.</li></ul><h3>The Forensic Standard vs. The Scam</h3><p>To see the truth, you must disable the digital makeup.</p><ul><li><strong>The Scammer Method:</strong> auto_bright_thr=0 and use_auto_wb=True. This stretches the histogram and normalizes temperatures to hide inconsistent light sources and photobashed seams.</li><li><strong>The Forensic Standard:</strong> Set no_auto_bright=True and use_auto_wb=False. This provides the raw, unweighted data, exposing the &quot;seams&quot; that the software otherwise hides.</li></ul><h3>What’s Motivation Behind the Fraud?</h3><p>While developing an analysis tool is straightforward, the real challenge is the coordinated suppression of dissent. The exposure of these histograms triggered an immediate sense of panic among those most invested in these images — specifically <strong>TJPowell, Tony Adams, Mick West, and BakerTuts</strong>.</p><p>Their reaction was inorganic and highly suspicious; the team shifted instantly into full damage control and went into a total alert mode to suppress technical findings. A dedicated group monitors these images 24/7 to prevent online discussion. For instance, whenever a forgery is exposed, Tony starts a Reddit thread as a moderator to allow his team to systematically attack anyone analyzing the files.</p><p>This team’s sole aim is to force fabricated images to be perceived as “Real.” Their ongoing hostility and “alert mode” tactics are designed to deter experts from releasing a comprehensive analysis. Authentic imagery does not require this level of gatekeeping.</p><p>— — — — — — — — — — — — — — — — —</p><h3>Full details</h3><h3>The Evidence Scammers Don’t Want You to See</h3><p>There is a coordinated effort to block investigation into the 19 “cloud” images currently being hosted on private drives. To prevent the fraud from being exposed, bad actors are using specific “anti-forensic” methods to hide the physical discrepancies in the files.</p><p><strong>Note to Investigators:</strong> Do not disclose specific forensic markers publicly before documenting them; doing so allows perpetrators to “patch” the images to hide tampering.</p><p>Link to file with 19 photos (These are still being hosted on the scammers personal drive. <strong>Do NOT disclose forensic discrepancies publicly</strong>, doing so enables the perpetrators to iterate on their techniques and ‘patch’ the images to hide tampering, making future investigation more challenging)</p><p><a href="https://drive.google.com/file/d/1JT0KOI1yJEtZVzdQtVBHWzyKujFDlBrb/view">https://drive.google.com/file/d/1JT0KOI1yJEtZVzdQtVBHWzyKujFDlBrb/view</a></p><p>For a rigorous forensic investigation, you should <strong>disable auto-scaling entirely, this is a common practice.</strong></p><blockquote><strong><em>Red Flag</em></strong><em>: Tony and the entire scammers team with vested interests insist on setting auto_bright_thr=0; Relying on </em><em>auto_bright_thr=0 while leaving auto-brightness </em><strong><em>on</em></strong><em> is a </em><strong><em>common &quot;anti-forensic&quot; tactic</em></strong><em>. It allows the software to consume the fabricated values of a </em><strong><em>modified RAW file to hide clipping and artifacts.</em></strong></blockquote><p>The auto_bright_thr=0 parameter in <strong>rawpy</strong> (a Python wrapper for <strong>LibRaw</strong>) is a high-stakes technical setting that <strong>directly impacts signal integrity in digital forensics.</strong></p><p>Tony’s argument that auto_bright_thr=0 &quot;assures no clipping takes place&quot; is used to mask evidence of manipulation. In forensics, Tony presents the case of beautification of the image, and makes a case for clipping when the histogram does not ever hit either the left or right of the histogram luminosity wall. Entire set of 19 images are flat set in the center of the histogram, unnatural, but these actors somehow kept pushing to keep the image wrapped up under heavy noise. Why?</p><p>The fabricated images histogram for luminosity hit the right wall of 255 only when scaled by softwares, not in it’s original raw data form. The RAW Histogram is set atifically in the center, <strong>which is unlikely to achieve in real world, and defninitely not for 19 images from the same set.</strong></p><ul><li><strong>Bad actors: Tony: </strong>By pushing for auto_bright_thr=0 instead of disabling auto-brightness entirely (no_auto_bright=True), an actor can still allow the software to apply a non-linear gain to the image. This shift can &quot;flood&quot; the image with noise, making it impossible to separate the <strong>signal from the noise, and visually identify the fraud.</strong></li><li>Baker’s argument is fundamentally flawed in a forensic context because it treats <strong>image development</strong> as a simple aesthetic choice rather than a <strong>signal integrity</strong> issue. Him advocating for auto_bright_thr=0, is effectively confessing that the images are synthetic and that masks are essential to avoid detecting the fraud.</li><li>Baker argues the noise is inherent, but setting the threshold to 0 often forces a default to the RAW file’s embedded metadata. In a forensic investigation, metadata from a suspected forgery is compromised evidence. Relying on these values forces an analysis through the creator’s curated settings rather than an objective <strong>sensor-to-luminosity mapping</strong>. The coordinated efforts by BakerTuts, TJPowell, and Tony Adams to block investigators and gatekeep these images are highly suspicious. Authentic imagery does not require a 24/7 internet gatekeepers.</li><li><strong>Masking Splicing</strong>: If someone has spliced a digital asset into a RAW file, auto-brightness can “blend” the edges of the fake object by re-scaling the luminosity of the entire frame.</li><li><strong>Histogram “Cleaning”</strong>: The clean bell curve Tony is showing in <strong>darktable</strong> is likely the result of this aggressive software scaling. A native Canon CMOS sensor would show <strong>stochastic fluctuations</strong> — tiny “teeth” or jitter in the histogram — caused by read noise. A perfectly smooth curve is a strong indicator of <strong>synthetic generation</strong> or heavy post-processing that has “ironed out” the sensor’s natural electrical signature.</li></ul><p><strong>Proof of Disinformation tactics targeted at me: Scammers </strong>have one weapon- dedicated ddisinformation team. It has become clear that a coordinated disinformation effort is being used to discredit and contain my findings rather than engage with the evidence.</p><p>They are betting that most people will not verify the source links and will instead accept confident sounding claims as fact.</p><blockquote><a href="https://www.reddit.com/r/AirlinerAbduction2014/comments/1afkckh/quest_for_the_fakery_files_the_cannon_saga/?share_id=B8B7dJMGrGdBx1tnvLCg_&amp;utm_content=1&amp;utm_medium=android_app&amp;utm_name=androidcss&amp;utm_source=share&amp;utm_term=1"><em>https://www.reddit.com/r/AirlinerAbduction2014/comments/1afkckh/quest_for_the_fakery_files_the_cannon_saga/?share_id=B8B7dJMGrGdBx1tnvLCg_&amp;utm_content=1&amp;utm_medium=android_app&amp;utm_name=androidcss&amp;utm_source=share&amp;utm_term=1</em></a></blockquote><p><strong>Notice “AirlinerAbduction2014” sub reddit is moderated by Tony Adams,</strong> BakerTuts and their fellow scammer group. They operate 24x7 anywhere on internet to protect their fabricated assets! WHY?</p><h3>The Scam operatives</h3><p>The Reddit sub mods and anons attacking individuals like me looking into publicly available images, and validating their claims shows coordinated narrative control rather than technical rebuttal: they monitor our activity, reframe timelines and quotes, then lean on forum authority and credential signaling while never engaging the specific measurable inconsistency you raised.</p><p><strong>That pattern is consistent with reputational containment and social pressure, not with a good faith forensic dispute over sensor physics.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RhdsOgGDgdtw5rM0PuZURA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Hzx2KDt-m7xM-WzY1CnLg.png" /></figure><p><strong>I ask journalists to review these links directly </strong>and assess whether the scammer’s claims are genuinely supported by the cited articles or part of a coordinated effort to target individuals who investigate these images beyond surface level viewing.</p><p>Scammers frequently use disinformation to deter scrutiny. While PeterWon makes bold allegations, site evidence reveals that the scammers are the actual harassers. Furthermore, he explicitly admits to <strong>cross-platform tracking</strong> of anyone investigating these images. What is the motive for this surveillance?”</p><p>Review the links to see how PeterWon is misrepresenting the facts. The harassment was directed at the OP and Mediatruth, not him. Verify the evidence for yourself</p><p>Scammers objective was to mask these photoshop patches using auto_bright_thr=0to stop fake cloud images from being exposed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bfa1pFHhVX1lbXTUalAGjw.png" /></figure><ul><li><strong>TJp’s Claim -1: “No clipping with default CR2 raw load settings” </strong>he presents a “clean” bell curve as proof of authenticity. However, a native Canon <strong>CR2 raw file</strong> is linear data; when loaded without processing, the histogram is typically heavily bunched toward the left (dark) side because it lacks gamma correction.</li><li><strong>Another attempt to stop investigation:</strong> By using “<strong>default settings</strong>,” he is admitting the software is applying auto-exposure, black-level offsets, and a tonal curve to the data. A “perfect” bell curve in a raw loader indicates the data has already been <strong>pre-developed</strong> or <strong>digitally shaped</strong> to appear as a standard image, rather than representing the raw sensor output.</li><li><strong>Tjp’s Claim-2: “Severe misapplication of black levels” he </strong>claims that “misapplied black levels” caused clipping in other versions. Canon sensors have a fixed, hardware-defined black point (typically 1024 or 2048), and we see no such dips in the histogram.</li><li><strong>Reason</strong>: If the image only looks “correct” when specific black levels are applied, it proves the signal is <strong>malleable and artificial</strong>. A physical sensor’s black level includes <strong>stochastic noise</strong> (CMOS fluctuations) that creates a jagged “jitter” at the bottom of the histogram. TJP’s histogram is mathematically smooth, a characteristic of <strong>synthetic distribution</strong> or heavy digital smoothing.</li><li><strong>TJp’s claim-3: Claim: “Saved as jpeg… it does not exhibit this clipping” : </strong>He lacks basic understanding of interpolation, gamma curves, and basic forensics. A Raw &gt; Jpeg is processed to optimize viewability and alters luminosity and RGB curves that masks image issues. For example in this image set, heavy high frequency noise was added to mask photobashing issues, and to bypass RAW Independent RGB channel noise variation.</li><li>Reason: Clipping is an exposure state, not a signature of authenticity. Saving to JPEG involves <strong>quantization</strong> and <strong>re-ranging</strong> the data. That the image “does not exhibit clipping” in a JPEG forensic tool only confirms that the highlights and shadows have been <strong>digitally scaled</strong> to fit within the 8-bit (0–255) container, masking any underlying sensor-level data loss or manipulation.</li></ul><h4>His own Histogram proves him wrong.</h4><p>TJP’s histogram shows an ideal, <strong>smooth Gaussian distribution</strong>. In a real-world capture of a complex scene like a mountain and clouds, a raw histogram would show multiple distinct peaks for the sky, clouds, and terrain. This “perfect” single bell curve is a hallmark of <strong>histogram matching</strong> or <strong>synthetic generation</strong>, where a computer-generated gradient is used to simulate natural light but lacks the entropy and read-noise “jitter” found in every genuine Canon DSLR capture.</p><p>These are the patches and artifacts that instaly show up on the images under basic forensic check.</p><p>In addition, most colors were adobe saturated colors and when forced to render natural Canon/natural profile colors, these adobe color patches get even more obvious.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wi8KDzqz6Mq4mspzb8z0mQ.png" /></figure><p>Another attempt to protect the forensic investigation and forcing everyone to only “View” the image as “intended”. Essentially, “Do Not Touch”</p><p>Let’s dive in</p><p>The line of code raw.postprocess(use_auto_wb=True, auto_bright_thr=0) is a &quot;black box&quot; operation that applies several transformations at once. By setting the threshold to 0, Tony is forcing the software to re-scale the entire image based on the single brightest pixel in the file. If he’s so keen on “Viewing” the image and appreciate the painting, he could use any RAW Viewer like Darktable, but he specifically followed me to “<a href="https://github.com/GuidoBartoli/sherloq/issues/86">Sherloq</a>” on Github to force a view only parameter. Ultimately this didnt help, as the there were just too many issues with the image to count.</p><p>Setting auto_bright_thr to 0 forces rawpy to scale the image relative to the absolute maximum value in the RAW data. This provides an optimized appearance that conceals structural flaws by applying the noise that was added by the photobasher, allowing the ‘fake image’ elements to appear seamless to the “casual observer”</p><p>By forcing auto_bright_thr=0, the Tony is forcing several layers of protection for a forged image:</p><p><strong>Dynamic Range Compression:</strong> Setting the threshold to 0 scales the entire image based on the absolute brightest pixel in the file. If a scammer has inserted a single ultra-bright “hot pixel” or artificial light source into a composite image, the rest of the image’s intensity values are compressed to the left of the histogram. This prevents local “blown out” areas (clipping) from being easily flagged by forensic software.</p><p><strong>Noise Flooding:</strong> Professionals in the forensics community are well aware that this setting “floods” the image with noise, making it nearly impossible to perform effective signal-to-noise separation. This noise acts as a “digital cloak,” masking the “seams” and artifacts that typically occur when one image is spliced into another.</p><p><strong>Forcing into Viewer mode:</strong> The code use_auto_wb=True and auto_bright_thr=0 together force the analysis to rely on the file’s internal metadata. In a suspected forgery, this metadata is often carefully calibrated to hide the fraud. By &quot;consuming&quot; these values, the investigator is effectively <strong>viewing</strong> the crime scene through the scammer’s intended lens. And any digging is strictly not allowed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*be25P8Jvza27XNXq-r1PPQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*LG7itjSnMLe6Y9TsuIPo8g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fOgtsO5zG6AE1Xg2u8iUbA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ggqWSMJkHw38Encr2FwIeg.png" /></figure><p>Tony’s argument is fundamentally flawed for any basic forensic test: The threshold at 0, the “image appears more homogeneous.” In forensics, “homogeneity” is <strong>exactly what you are trying to <em>avoid</em> or <em>investigate</em></strong>. By smoothing out the signal or scaling it to fit a specific container, you might be masking the very noise patterns or sensor-level inconsistencies that prove a forgery. “Homogenization” flattens the histogram. Subtle noise patterns or “seams” between a fake object and a real background become much harder to see because the signal-to-noise ratio is artificially lowered across the board.</p><h3>What’s their motivation for hiding the fake cloud fraud?</h3><p>While developing a good analysis tool is straightforward, the real challenge lies in the coordinated suppression of dissent. The exposure of these histograms triggered an immediate sense of panic among those most invested in these images — specifically <strong>TJPowell, Tony Adams, Mick West, and BakerTuts</strong>. Their reaction was inorganic and highly suspicious; the team shifted instantly into full damage control and went into a total alert mode to suppress the technical findings rather than addressing the evidence.</p><p>A dedicated group monitors these images constantly to prevent discussion online. For instance, whenever a discussion exposes the forgery, Tony starts a Reddit thread where he acts as the moderator, allowing his team to systematically attack anyone attempting to analyze the files. This suspicious team’s sole aim is to force these fabricated images to be perceived as “Real.” The motives behind this gatekeeping remain unclear, especially since this situation offered a prime opportunity for public education on image forensics. Instead, their ongoing hostility and “alert mode” tactics are designed to deter experts from releasing comprehensive analyses.</p><h3>Summary: Manipulation vs. Integrity</h3><p><strong>The Trick:</strong> Setting auto_bright_thr to <strong>0</strong> and use_auto_wb to <strong>True</strong> stretches the histogram and normalizes color temperatures. This masks inconsistent noise and different light sources, making a &quot;photobashed&quot; composite look like a single, authentic capture.</p><p><strong>The Forensic Standard:</strong></p><ul><li><strong>auto_bright_thr</strong>: Set to <strong>0.01 or higher</strong> (Exposes noise disparities and impossible clipping).</li><li><strong>use_auto_wb</strong>: Set to <strong>False</strong> (Prevents the software from hiding mismatched light temperatures between the clouds and the sky).</li></ul><p><strong>The Evidence:</strong> Disabling these auto-adjustments provides the “hard proof” by revealing the raw, unweighted data. It exposes the “seams” of the forgery that the software otherwise hides to improve viewability.</p><p>Finally here’s the settings in Rawpy for diffirent use cases</p><p>Fake image gatekeepers are forcing the settings that “Mask” glaring issues in the image, while a true forensic need different set of parameters to be set. <br>here’s a guide for reference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LHhNF3_WEf5JPRgorlxKLg.png" /></figure><p>Here’s another <a href="https://github.com/GuidoBartoli/sherloq/issues/93">comment</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qzv8ffUTq4uAHz7M0x_zHw.png" /></figure><p>This guy BakerTutz is clueless , he cant tell the difference bwteeen — data, viewability, and forensics. You are not “throwing away” data; you are <strong>isolating</strong> it. 0.01 (or higher) is the “Forensic” <strong>choice</strong> for a reason. May be these guys should use image viewers and not bother with investigation.</p><ul><li><strong>Clipping is Evidence:</strong> In forensics, we <em>want</em> to see where the sensor clipped. If a cloud is “pasted” in, its clipping point and noise profile will not match the rest of the RAW data.</li><li><strong>Linear Accuracy:</strong> A small threshold (0.01+) ensures that the scaling is calculated from a statistically significant set of pixels rather than a single potentially manipulated hot pixel or “pasted” highlight.</li></ul><p>Another one! Can you tell what the problem is with this comment?</p><ul><li>Another strangely disguised way of forcing “View” only mode. Viewing is allowed, investigation is NOT. That’s pretty much it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i6kD1D1LM_29wuEtjbjRYg.png" /></figure><h3>FAQ for Journalists.</h3><p><strong>Scammer Claim 1: “Using </strong><strong>auto_bright_thr=0 ensures no clipping takes place.”</strong></p><ul><li><strong>The Reality:</strong> In forensics, we <em>want</em> to see the clipping. Authentic sensor data has messy, jagged edges where light exceeds the sensor’s capacity. By forcing the threshold to zero, you are “homogenizing” the image — stretching the data to hide the very artifacts and “pasted” elements we are looking for. It is a tool for beautification, not investigation.</li></ul><p><strong>Scammer Claim 2: “You are ‘throwing away data’ by disabling auto-brightness.”</strong></p><ul><li><strong>The Reality:</strong> False. Disabling auto-adjustments (using no_auto_bright=True) is the only way to isolate the raw signal. We aren&#39;t throwing data away; we are stripping off the digital makeup. Real forensics requires a linear, unweighted view of the sensor to see where the fraud begins and the reality ends.</li></ul><p><strong>Scammer Claim 3: “A smooth bell curve in the histogram proves the image is natural.”</strong></p><ul><li><strong>The Reality:</strong> A “perfect” bell curve in a RAW loader is a hallmark of synthetic generation. A genuine Canon 5D Mark II capture of complex clouds and mountains would show multiple distinct peaks and stochastic “teeth” (jitter) caused by read noise. A perfectly smooth curve suggests the data has been digitally shaped to <em>look</em> like a photo.</li></ul><p><strong>Scammer Claim 4: “These settings are just standard ‘default’ RAW load settings.”</strong></p><ul><li><strong>The Reality:</strong> Relying on “defaults” is an admission that you are letting software pre-develop the image. Forgery detection requires looking at the raw sensor output before the software applies auto-exposure, black-level offsets, and tonal curves. “Default” settings are designed to make an image look good; forensic settings are designed to make the truth visible.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d76a7fc5d8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Smoking Gun: How cloud Images used for spreading disinformation are proven fake.]]></title>
            <link>https://medium.com/@Fastlane90/the-smoking-gun-how-cloud-images-used-for-spreading-disinformation-are-proven-fake-e43104f522b8?source=rss-63141a9ae671------2</link>
            <guid isPermaLink="false">https://medium.com/p/e43104f522b8</guid>
            <category><![CDATA[vfx]]></category>
            <category><![CDATA[disinformation]]></category>
            <dc:creator><![CDATA[CasualObserver]]></dc:creator>
            <pubDate>Thu, 25 Dec 2025 17:09:16 GMT</pubDate>
            <atom:updated>2026-01-13T15:34:13.562Z</atom:updated>
            <content:encoded><![CDATA[<h3>Jonas RAW Cloud Images- All Proven Fake Scientifically. Here’s how</h3><h3>Context</h3><p>The authenticity of a dataset containing 19 RAW image files (IMG_1828 through IMG_1855), commonly referred to as the “Jonas” set, has been disputed. These files are presented as native, original captures taken in January 2012 using a Canon EOS 5D Mark II.</p><p>The forensic question is binary: Do these 19 CR2 files contain the original sensor data expected from a 2012 Canon hardware capture, or do they show statistical anomalies consistent with post-processing and file manipulation? This analysis conducts a hardware-level audit of the noise floor across the entire set to verify their origin.</p><p>This article moves beyond visual inspection to perform a forensic audit of the file data itself. By analyzing the “noise floor” — the random distribution of pixel values at the sensor level — we can determine if the files adhere to the physical constraints of the hardware they claim to originate from.</p><h3>Hypothesis</h3><p>If the “Jonas” CR2 files are authentic native captures, they must exhibit the physical characteristics of a Canon 5D Mark II sensor. Specifically, we test the hypothesis that <strong>genuine optical captures must contain a ‘noise floor.’</strong></p><p>Even in a high-key (bright) image, the sensor is never perfectly silent. Read noise (electronic interference) creates a Gaussian distribution of values that anchors the data to the hardware’s black level. If these files are genuine, we expect to see a tapered tail of noise extending down to the black point. If they are manipulated, we hypothesize the presence of a “dead zone” or mathematical void inconsistent with sensor physics.</p><h3>3. Methodology</h3><p>To ensure the results are based on raw sensor data rather than interpreted images, this analysis utilizes a specific workflow designed to bypass automatic correction.</p><ul><li><strong>Tools:</strong> We utilized RawTherapee (v5.8+) for visual histogram inspection and a custom Python script using the rawpy library for statistical plotting.</li><li><strong>Linear Analysis:</strong> Critical to this method is disabling all “Auto-Bright,” “Demosaicing,” and “Denoising” features. We analyze the <strong>Linear RAW data</strong> (before gamma correction) to view the actual photon count per pixel.</li><li><strong>Control Group:</strong> We compared the questionable files against verified control samples from the Canon 5D Mark II, sourced from independent review sites and archives (2008–2012 era).</li></ul><p><em>(The Python code used to generate the logarithmic histograms is provided at the end of this article for independent verification.)</em></p><h3>Results</h3><p>When plotting the pixel frequency on a logarithmic scale, a distinct anomaly appears across <strong>all 19 files</strong> in the test group compared to the control group13131313.</p><p>The Control Group (Authentic 5D Mk II)</p><p>In every verified control sample, regardless of exposure settings, we observe a “tapered tail.” The data curve slopes gently downward to the left, statistically overlapping with the camera’s hardware black level (typically value 1024 for this sensor)14141414. This indicates the presence of natural read noise15.+2</p><p>The Test Group (All 19 Jonas Files)</p><p>In the suspect files (IMG_1828–1855), this tail is consistently absent. Instead, the data exhibits two specific anomalies:</p><ol><li><strong>A Vertical Cliff:</strong> The pixel counts hit a “hard stop” around value 1070–1100, rather than tapering off16161616.</li><li><strong>A Dead Zone:</strong> There is a mathematical gap of nearly 50–100 levels between the hardware black level and the image payload where effectively zero pixels exist17171717.</li></ol><h3><strong>Data Interpretation: Logarithmic vs. Linear Displays</strong></h3><p>Readers may observe that the forensic charts presented here appear “curved” while standard RawTherapee histograms appear “spiked”18. This is a difference in display scaling, not data integrity.</p><ul><li><strong>The Forensic Charts (Logarithmic Scale):</strong> The Python script utilizes a Logarithmic Y-Axis ($1, 10, 100, 10⁴$). This acts like “night vision,” amplifying minute details in the low-count areas to ensure the noise floor is clearly visible19.</li><li><strong>RawTherapee (Linear Scale):</strong> Standard histograms use a Linear Y-Axis. Because the image has low contrast, the data stacks vertically, creating a “thin tower” appearance20.</li></ul><p>Despite the visual difference in shape, both methods confirm the exact same anomaly: a “Dead Zone” in the 0–50 range where the signal is mathematically disconnected from the hardware black level</p><h3>Directly observable technical facts:</h3><ol><li>Histogram and noise floor behavior<br>When examined in raw linear mode (RawTherapee neutral profile or rawpy/dcraw with no demosaic/black subtraction applied beyond hardware level):</li></ol><ul><li>All 19 files show shadow values starting abruptly at a non-zero minimum (effective gap of dozens to hundreds of ADU below the data floor).</li><li>No gradual Gaussian noise tail extends down to or overlaps the optical black level as measured from the sensor’s masked pixels.</li><li>This absence of read-noise distribution in the lowest bins is physically inconsistent with how CMOS sensors (including the 5D Mark II) record data. Real sensor output always includes read noise, thermal noise, and shot noise that produce values distributed around the black level offset.</li></ul><p><strong>2. Repeatable verification</strong><br>Publicly available genuine 5D Mark II CR2 samples (e.g., review sites, raw sample archives from 2008–2012 era) uniformly show the expected noise tail overlapping the black level when plotted the same way. The difference is measurable and consistent across controls.</p><p><strong>3. Statistical anomalies across the set</strong><br>Multiple files exhibit near-identical mean channel values to many decimal places and identical standard deviations in certain channels — improbable for separate real-world exposures even seconds apart under stable lighting.</p><p><strong>4. Scene-level inconsistencies</strong><br>Overlay comparisons with earlier published versions of similar Mt. Fuji aerial shots (2012 texture library uploads) reveal pixel-level additions/removals (snow patches, cloud edges) that do not align with natural variation between frames.</p><p><strong>5. File structure vs. content</strong><br>The CR2 container passes basic structural integrity checks (valid thumbnails, metadata, Bayer pattern). This is achievable through known reverse-engineering of the format. The anomalies are in the sensor data payload itself, not the wrapper.</p><h3><strong>Conclusion from measurable evidence only:</strong></h3><p>The image data inside these 19 CR2 files <strong>did not originate directly from a Canon EOS 5D Mark II sensor in native capture mode.</strong> The contents show clear signs of post-capture assembly or adjustment (most likely compositing followed by black-point lifting and repackaging into RAW containers). This is not an opinion derived from what others say, it is a direct consequence of the data violating expected sensor noise physics and showing internal statistical/scene inconsistencies.</p><blockquote><em>19 fake RAW cloud files: Originally shared by Jonas: </em><a href="https://drive.google.com/file/d/1JT0KOI1yJEtZVzdQtVBHWzyKujFDlBrb/view?usp=sharing"><em>https://drive.google.com/file/d/1JT0KOI1yJEtZVzdQtVBHWzyKujFDlBrb/view?usp=sharing</em></a></blockquote><blockquote><em>Alternate link , when he deletes his link or modifies the files: </em><a href="https://drive.google.com/drive/folders/1NQ-ac7PMeGZPLTFXykhnjUudHqnl-SMv?usp=sharing"><em>https://drive.google.com/drive/folders/1NQ-ac7PMeGZPLTFXykhnjUudHqnl-SMv?usp=sharing</em></a></blockquote><p><strong>Jonas Fake Cloud Photobashed Image Histogram</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*BaDA6po5m5M6jwstdvLb9A.png" /><figcaption>An impossible real world RAW image Histogram from Jonas fake cloud image set</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*AE6_dzM0JZV-ZZ7yrX7pWQ.png" /><figcaption>14Bit Jonas fake img_1844.CR2 Histogram</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*qOaqHE51auYiN_zX0EiJ4Q.png" /><figcaption>Authentic Canon 5D Mark II CR2</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kjvaRNG4YLOINTk2UzTUrQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*z5SHS31fypSuYE1nXIM_bw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*0jsnBVwSFBArnc8Yt3DzEA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*fRG1MZsOMAy2MP629P7RRQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*EKJPVJbneSbPBapLLBzZgA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*1wM0_M-9CAddDD-2t-wvUg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*bCFZFMYWKn75juPn5bem8Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*P2RNYioIcqZRhi-F5OKl2Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*IWzGqvxENGRD3p6m33saXg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*FFWnZ1hWSuS-DhKi4g97sg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*5KOBNmwk-aWsWMf-4Q9yBA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*m_Vmczeq4bk0QMTyyccAdw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*mPJhxxA7vZPxTw7usAXi-Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*oZKQbovszm0OI8R_sZVTvQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*V6gkeSjZM4WFEBBQ4MPMNQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*AE6_dzM0JZV-ZZ7yrX7pWQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*gb4Qc11o6GXbzBrYNSX_rw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*z-KQ2KkJBJ6Gn74LHBan2g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*4wYsGaBwlFBRhU9kHy57zQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*SA3z-JuHcWYMXrWH5-9WZg.png" /><figcaption>All 19 Jonas Fake Cloud Image 14 Bit -Histograms (RED)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*WlcncTImUfGtLoVrWr_QSA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*jBFJ0rTfk6sWtwkYmy8gDQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Yu0VlDTQFLkR8_HlRbM6zQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*QKzpWpSat6o2bYGYwkYgsw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*qOaqHE51auYiN_zX0EiJ4Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*UxLxT6UKrLmACFjY3VnuPg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*jn4MVOo53eicUihCiynKjw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*KsK66CF-_O3PDUxGxZVr8A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*BO8Cwur30TxrIAAFD8bQCQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*R5f07rZnDG3im0Z2qgGQyQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*_rQsILhrLyDCcKeE-UR_ZA.png" /><figcaption>Real Authentic Canon CR2 14 Bit Histograms (Blue)</figcaption></figure><p>The 14-bit histograms provide the definitive proof: the Jonas Cloud Images violate the laws of physics. In every verified Canon 5D Mark II file, the “tapered tail” of electrical read noise is present, anchoring the image to the hardware floor.</p><p>In the Jonas Cloud set, that tail is absent, which is a a signature of Day light imaging. The histograms exhibit a “Vertical Cliff” and a “Dead Zone” of absolute mathematical silence. A physical sensor cannot record a scene while simultaneously recording zero electrons of noise.</p><h4><strong>This is the digital fingerprint of a human using a “Black Point” slider in Photoshop to hide the seams of a photobashed composite.</strong></h4><p>The inorganic panic and “red alert” damage control from individuals like <strong>TJPowell, Tony Adams, and BakerTuts</strong> is now explained. They are protecting a forgery that cannot survive a 14-bit forensic audit.</p><p>— — — — — — — — — — — — — — — — — — — — — — -</p><h3>Details and more Histogram analysis</h3><p><strong>CRITICAL STEP: Lock the Evidence</strong> Now that this debunking is public, the perpetrators will likely attempt to “scrub” their files — adding fake noise to black levels to hide the fraud. Since these files are hosted on a personal Google Drive, they can be altered at any moment to fit the narrative.</p><p><strong>Take Action:</strong></p><ol><li><strong>Run the Hashes:</strong> Use the <a href="https://docs.google.com/document/d/e/2PACX-1vSG0pYfYdx1WsmkDsRU-Rlo642QFaqXSjfnjUmLyp4qFMiK4mU-HX3HjYdRRrFoN6me4rpCHEAISsHQ/pub">code</a> at the bottom to generate MD5 and SHA-256 hashes of the current files immediately.</li><li><strong>Compare:</strong> Save these hashes. If the files change tomorrow, the mismatched hashes will serve as proof of tampering.</li></ol><p><strong><em>(Scroll down for FAQ and Code)</em></strong></p><p><em>Preliminary Note: Histogram analysis quickly confirms these 19 images are fraudulent. Beyond that, over 30 significant discrepancies exist, providing definitive proof of manipulation.</em></p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — -</p><h3>Starting from quick basics</h3><h3>How a Camera Actually “Sees” (A Simple Guide)</h3><p>To understand the fraud, you first need to understand how a digital camera captures reality. It isn’t magic; it’s just counting.</p><p><strong>1. The “Rain Gauge” Analogy</strong> Imagine your camera sensor is a grid of millions of tiny buckets (pixels). When you open the shutter, light photons rain down into these buckets like water.</p><ul><li><strong>Bright areas (Clouds):</strong> The buckets fill up to the brim.</li><li><strong>Dark areas (Shadows):</strong> Only a few drops land in the bucket.</li><li><strong>Pure Darkness:</strong> Even with the lens cap on, the bucket isn’t perfectly dry. There is always a tiny bit of “moisture” from humidity or condensation. In a camera, this is <strong>electricity</strong>. The sensor itself hums with a tiny voltage called the “Noise Floor.” A real bucket is never 100% empty.</li></ul><p><strong>2. Turning Light into Numbers</strong> Once the shutter closes, the camera measures the “water” in each bucket and gives it a number.</p><ul><li><strong>14-bit RAW:</strong> The camera can count from <strong>0 up to 16,383</strong>. This gives it incredible precision to distinguish between “almost dark” and “slightly less dark.”</li><li><strong>8-bit JPEG:</strong> To save space, the camera crushes that huge range down to <strong>0–255</strong>. It throws away the subtle details.</li></ul><p><strong>3. The Mosaic (RGGB)</strong></p><p>Sensors are colorblind; they only measure brightness (intensity). To see color, they wear a checkerboard filter of Red, Green, and Blue glasses (called the Bayer Pattern).</p><ul><li>One pixel measures Red intensity.</li><li>One measures Blue.</li><li>Two measure Green. The camera later “interpolates” (guesses) the missing colors based on the neighbors to create the final image.</li></ul><h3>Reading the Histogram: The “Brightness Census”</h3><p>The histogram is simply a graph that counts the buckets. <a href="https://photographylife.com/what-are-histograms-a-photographers-guide">A great reference if you like to read.</a></p><ul><li><strong>Left Side (towards 0):</strong> The Shadows. This is where your dark mountains and deep craters live.</li><li><strong>Right Side (towards 255 or 16,383):</strong> The Highlights. This is where the bright white clouds live.</li><li><strong>The Height:</strong> How many pixels are at that exact brightness.</li></ul><p><strong>Why the “Noise Floor” is the Smoking Gun</strong></p><p>To understand why these images are fake, you have to understand how the physical world works.</p><p><strong>The “Microphone” Rule</strong> Think of a camera sensor like a microphone recording a room. Even in a perfectly quiet room, a sensitive microphone picks up a faint “hiss” or static. It’s unavoidable electrical background noise.</p><p>In photography, we call this the <strong>Noise Floor</strong>.</p><ul><li><strong>Real RAW File:</strong> The data graph (histogram) looks like a slide or a ramp. It starts at the very bottom left and ramps up. That ramp is the visual version of that microphone hiss. It represents the “electrical moisture” that always exists in the bucket.</li><li><strong>The Suspect File:</strong> These files look like an audio recording of a crowded city that suddenly goes mathematically silent for three seconds, exactly across 19 images. That kind of “dead air” doesn’t happen in nature- unless you pasted the processed audio file ( just audio without noise) on to an empty tape.</li></ul><p><strong>The Impossible Gap</strong> When we look at the data for these images, it doesn’t ramp up from the floor. Instead, the data starts abruptly in mid-air, leaving a massive, empty gap of “zero pixels” on the left.</p><p>Critics will try to tell you this is just a camera setting (a “black level”). It is not. This is a violation of physics. That empty gap is the visual equivalent of a vacuum. It only happens when someone edits the file in a studio where just the image is maufactured ( Photoshop) without real world noise. hitting the sensor. Noise is not the image fog, but the actual light that the sensor must discard to generate the image, and this noise starts from the calculated sensor floor ( not the static 1023/1024)</p><h3>Methodology</h3><p>To ensure the results are based on raw sensor data rather than interpreted images, this analysis utilizes a specific workflow designed to bypass automatic correction.</p><ul><li><strong>Tools:</strong> We utilized RawTherapee (v5.8+) for visual histogram inspection and a custom Python script using the rawpy library for statistical plotting.</li><li><strong>Linear Analysis:</strong> Critical to this method is disabling all “Auto-Bright,” “Demosaicing,” and “Denoising” features. We analyze the <strong>Linear RAW data</strong> (before gamma correction) to view the actual photon count per pixel.</li><li><strong>Control Group:</strong> We compared the questionable files against verified control samples from the Canon 5D Mark II, sourced from independent review sites and archives (2008–2012 era).</li></ul><p><em>(The Python code used to generate the logarithmic histograms is provided at the end of this article for independent verification.)</em></p><h3>Results</h3><p>When plotting the pixel frequency on a logarithmic scale, a distinct anomaly appears in the test group (Jonas files) compared to the control group.</p><p><strong>The Control Group (Authentic 5D Mk II)</strong> In every verified control sample, regardless of exposure settings, we observe a “tapered tail.” The data curve slopes gently downward to the left, statistically overlapping with the camera’s hardware black level (typically value 1024 for this sensor). This indicates the presence of natural read noise.</p><p><strong>The Test Group (Jonas Files)</strong> In the suspect files (IMG_1828–1845), this tail is absent. Instead, the data exhibits two specific anomalies:</p><ol><li><strong>A Vertical Cliff:</strong> The pixel counts hit a “hard stop” around value 1070–1100, rather than tapering off.</li><li><strong>A Dead Zone:</strong> There is a mathematical gap of nearly 50–100 levels between the hardware black level and the image payload where effectively zero pixels exist.</li></ol><figure><img alt="Jonas Fake RAW Cloud image Histogram" src="https://cdn-images-1.medium.com/max/1024/0*iF7BwAXv27_9PZ71.png" /></figure><figure><img alt="a Genuine Canon EOS 5D Mark II Histogram- Notice the histogram spread" src="https://cdn-images-1.medium.com/max/1024/0*_w2jLGvwejOoxXdB.png" /></figure><h3>Discussion and Limitations</h3><p>The presence of this “Dead Zone” is a significant forensic red flag. A common counter-argument is that because these are high-key aerial photographs of bright clouds, there should naturally be no pixels in the deep shadow range.</p><p>However, this interpretation conflates <strong>Shot Noise</strong> (light signal) with <strong>Read Noise</strong> (hardware floor). While a bright scene has high signal values, the sensor’s hardware always generates a baseline Gaussian distribution of electronic noise independent of the scene.</p><p><strong>The Physics of the “Dead Zone”</strong> If these were genuine bright exposures, the histogram data would shift to the right, but the “tail” of the read noise should still anchor the signal to the black point. A physical sensor cannot record light while simultaneously recording “absolute mathematical silence” in the lower registers. The “Vertical Cliff” observed in all 19 files implies that data below a certain threshold was mathematically clipped (e.g., via a “Black Point” adjustment), which is inconsistent with a native RAW capture.</p><p><strong>5.1 Case Study: The Mt. Fuji Shadow Anomaly</strong> The “Deep Shadows” critique is further invalidated by the content of the image itself. The file IMG_1843.CR2 clearly depicts the Mt. Fuji crater—a region of deep shadow.</p><ul><li><strong>Visual Observation:</strong> The crater contains deep darks that, in a native optical capture, would drive the signal down toward the noise floor (values 0–10 above Black Level).</li><li><strong>Histogram Data:</strong> Contradicting the visual reality, the histogram shows a complete absence of data in these blacks. The “darkest” pixels start abruptly at level 50.</li></ul><p>This creates a paradox: the crater shadows are <strong>visually dark</strong> but <strong>mathematically bright</strong>. This decoupling of visual shadow from the sensor’s noise floor is impossible in a single-exposure native capture and strongly suggests the black point was artificially lifted.</p><p><strong>5.2 Addressing Technical Counter-Arguments</strong></p><ul><li><strong>Claim: “It’s just underexposed.”</strong></li><li><em>Rebuttal:</em> Underexposure creates <em>more</em> noise, not silence. If a sensor struggles in the dark, it generates static (read noise). These images have empty data, which is the fingerprint of a software slider, not a camera shutter.</li><li><strong>Claim: “The black level is 1023.”</strong></li><li><em>Rebuttal:</em> 1023 is a calibration setting. In genuine files, pixels statistically overlap this level due to noise. In the Jonas files, there is a clean, artificial gap between the Optical Black (masked pixels) and the image data.</li><li><strong>Claim: “In-camera settings (High Contrast) caused this.”</strong></li><li><em>Rebuttal:</em> Picture Styles affect JPEGs, not RAW data. No Canon menu option creates a mathematical null value for the first 50 shades of light.</li></ul><h3>Data Interpretation: Logarithmic vs. Linear Displays</h3><p>Readers may observe that the custom forensic charts appear “curved” while the RawTherapee histograms appear “spiked.” This is a difference in display scaling, not data integrity.</p><p>* <strong>The Forensic Charts (Logarithmic Scale):</strong> The Python script utilizes a Logarithmic Y-Axis (1, 10, 100, 10,000). This scaling acts like “night vision,” amplifying minute details in the low-count areas to ensure the noise floor is clearly visible. * <strong>RawTherapee (Linear Scale):</strong> The standard histogram uses a Linear Y-Axis. Because the image has low contrast, the data stacks vertically, creating a “thin tower” appearance.</p><p>Despite the visual difference in shape, both methods confirm the exact same anomaly: a “Dead Zone” in the 0–50 range. Whether analyzed on a linear or logarithmic scale, the signal is disconnected from the left axis</p><h3>Verification Resources (Open Source Code)</h3><p>To allow for independent peer review, the Python <a href="https://docs.google.com/document/d/e/2PACX-1vSG0pYfYdx1WsmkDsRU-Rlo642QFaqXSjfnjUmLyp4qFMiK4mU-HX3HjYdRRrFoN6me4rpCHEAISsHQ/pub">code</a> used to generate these forensic audits is provided below. This script extracts the raw sensor data and plots it on a Logarithmic Scale, revealing shadow details that standard linear histograms may compress or obscure.</p><p>We encourage skeptics and analysts to download the suspect CR2 files and run this script to verify the findings independently. The methodology relies on reproducible mathematical data, not subjective interpretation</p><p>— — — — — — — — — — — — — — — — — — — — — — — — -</p><h4>Baseline</h4><h4>Here are some baseline histograms of real pictures taken using Canon 5D mark II.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ELcdgzkhM-eLfK-tbEp5OA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BfIxudcOO2thgi-AEMHsww.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lk66kZMAA_0JVcdLf-BFYw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_mZTqyS1DgxBs_haZYzluQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2vWOHuezv3VQ0ovni0ZepQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ppwbGuXKtoOjKcwr6XOyhA.png" /></figure><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — -</p><p>None of the 19 cloud images being shared online are authentic; a quick test of any sample proves they are fabricated.</p><h4><strong>Jonas IMG_1828.cr2 Histogram</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fzSwQ98OBxkhnmb2gGhfYA.png" /><figcaption>1828 Luminosity Histogram</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BaDA6po5m5M6jwstdvLb9A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lzRA8x4KVnDsgWVJJfVShQ.png" /></figure><h4>Jonas IMG_1839.cr2 Histogram</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G6pBeIVxPPXafK_sJis4uA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vN3Qfu62d1fxn0Vt993pOg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cn9finB3i66N98rvf19kww.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sDqu35VabXSyLtM9SkMEBQ.png" /></figure><h4>Jonas IMG_1843.cr2 Histogram</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DoIYWwBJaI1IoEPoefjZQA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C9CsJ-DHZ-I9gDVUdRJL7g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7l5ETVc2i4WeysBZonLWFQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nQGor-VPnFG2_00_GZmILQ.png" /></figure><p>The 1843 file displays the same fraudulent “dead zone” anomaly — visually dark shadows in the clouds and mountain that mathematically float at pixel level 30, proving the black point was artificially lifted to hide the lack of genuine sensor noise.</p><h4>Jonas IMG_1844.cr2 Histogram</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hkl3VerIedHyYeUwZ8gpMg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0BsgSnHvnjnnYSgPWSVGng.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pNGQnaag1eIkVRWr083YPA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NrA-ay6o6Ggs580i_cDq4A.png" /></figure><h4>Jonas IMG_1845.cr2 Histogram</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OxRnP2RPP459q5JHijfueA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N2ctOHlFgJ-5hvF7d4eAXw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*41MPmB8QG7Q4AToltkuV9g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X2OycI7nnGzUZcwPqYIChw.png" /></figure><p>Real cameras are noisy. They are messy. They record static in the shadows because that is how electricity works.</p><p>Debunkers on social media — X and Reddit — lack the technical grounding to distinguish fact from fabrication. It’s increasingly getting obvious that for some it’s a necessity to be effective at disinformation spread, they push a prepackaged narrative they were handed. I understand it’s their job to suppress some videos, but facts are facts, these images are too easy to spot as fakes.</p><h3>6. Conclusion</h3><p>The 19 “Jonas” CR2 files exhibit a noise profile that contradicts the known hardware behavior of the Canon 5D Mark II. While the visual content portrays a bright cloudscape, the underlying data reveals a “cleaned” noise floor inconsistent with raw optical capture. The measurable evidence indicates these files are not camera originals but likely reconstructed or manipulated containers.</p><h3>7. Verification Resources</h3><p>To allow for independent peer review, the Python code used to generate these forensic audits is provided below. We encourage analysts to download the suspect CR2 files and run this script to verify the findings independently.</p><p>Python <a href="https://docs.google.com/document/d/e/2PACX-1vSG0pYfYdx1WsmkDsRU-Rlo642QFaqXSjfnjUmLyp4qFMiK4mU-HX3HjYdRRrFoN6me4rpCHEAISsHQ/pub">code</a></p><h3>— — — — — — — —</h3><h3><strong><em>Potential deflections:</em></strong></h3><p><strong><em>Specific individuals from r/Airlinerabduction2014 subreddit </em></strong><em>who actively shield and distribute these forgeries are incentivized to protect them. Expect deflection, bad-faith arguments, and coordinated damage control rather than any serious engagement with the technical evidence.</em></p><p>The exposure of these histograms triggered an immediate sense of panic among those most invested in the images — specifically <strong>TJPowell, Tony Adams, and BakerTuts</strong>. Their reaction was inorganic and highly suspicious; they shifted instantly into full damage control, entering a state of high alert to suppress the technical findings rather than addressing them</p><h3>Anticipating Rebuttals: Core Clarifications Before Any Debate</h3><p><strong>Claim 1: “The Photographer used a specific Picture Style, High Contrast, or Monochrome setting.”</strong></p><ul><li><strong>The Reality:</strong> False. In-camera settings like “High Contrast” or “Monochrome” affect the JPEG preview, but they <strong>do not</strong> delete raw sensor data in a CR2 file. A RAW file captures what the sensor saw, not what the settings processed. No menu option in a Canon camera creates a mathematical null value for the first 50 shades of light.</li></ul><p><strong>Claim 2: “It’s just underexposed” or “Dark scenes/clouds may not produce values near black.”</strong></p><ul><li><strong>The Reality:</strong> False. Underexposure creates <em>more</em> noise, not silence. If you take a photo in the dark, the sensor struggles and generates static (read noise). These images don’t have static; they have empty data. Even if the darkest part of the scene is bright, pixel variance still populates values down to the electronic floor. That “dead zone” is the fingerprint of the “Black Point” slider in Photoshop, not a camera shutter.</li></ul><p><strong>Claim 3: “The black level is 1023. Image data does not have to start at 1023.”</strong></p><ul><li><strong>The Reality:</strong> This argument confuses metadata with physics. The value “1023” is just a calibration setting. In a genuine RAW capture, the darkest image pixels statistically overlap with the “Optical Black” pixels (the masked border of the sensor). Both are produced by the same electronics at the same moment. In these fake files, there is a clean,large wide artificial gap between the Optical Black and the image data . No exposure setting explains this separation. This is a signature synthetic image grafted into a donor CR2 work.</li></ul><p><strong>Claim 4: “Noise reduction, debayering, or RAW converters can cause the gap.”</strong></p><ul><li><strong>The Reality:</strong> False. The histograms shown are from <strong>Linear RAW values</strong>, measured before any gamma correction, denoising, or demosaicing occurred. Additionally, if the camera itself had applied noise reduction, it would have affected the masked border pixels too. It didn’t. The gap persists across every tool and viewer, proving the data was altered selectively on the image only.</li></ul><p><strong>Claim 5: “Canon or experts said the files are legitimate.”</strong></p><ul><li><strong>The Reality:</strong> Canon actually <strong>confirmed that the specific “Jonas” CR2 files presented to them are fabricated,</strong> and they explicitly warned that CR2 files should not be assumed uneditable. Forensics is not decided by general opinions like “I see no obvious tampering.” It is decided by whether physical constraints are violated. A persistent, repeatable dead zone between optical black and active pixel data is a hardware impossibility.</li></ul><p><strong>Claim 6: “Some cameras have lifted blacks or clipping.”</strong></p><ul><li><strong>The Reality:</strong> When a camera lifts blacks, it affects <strong>both</strong> the masked border pixels and the active image pixels equally. In these files, we see a distinct asymmetry: the masked pixels show a normal noise floor, while the active pixels show an elevated minimum with zero overlap. That specific discrepancy cannot arise from in-camera processing.</li></ul><p><strong>Claim 7: “Histograms alone are not proof.”</strong></p><ul><li><strong>The Reality:</strong> In this context, they are. A histogram combined with masked pixel analysis is not a cosmetic statistic; it is a direct measurement of sensor output. We are identifying <strong>missing code values</strong> that must exist in any genuine electrical capture. This is a hardware-level inconsistency, not an aesthetic judgment.</li></ul><p><strong>Claim 8: “This could be an edge case or rare behavior.”</strong></p><ul><li><strong>The Reality:</strong> Edge cases are random and inconsistent. These files show the exact same gap and the exact same structure across multiple images. That indicates a <strong>systematic process</strong> (a human workflow), not a random sensor behavior.</li></ul><p><strong>Scaller Claim 9 “The Photographer used a specific Picture Style or Setting.”</strong></p><ul><li><strong>The Reality:</strong> False. In-camera settings like “High Contrast” or “Monochrome” affect the JPEG preview, but they <strong>do not</strong> delete raw sensor data in a CR2 file. A RAW file captures what the sensor saw, not what the settings processed. No menu option in a Canon camera creates a mathematical null value for the first 50 shades of light.</li></ul><p><strong>Claim 10: “It’s just underexposed.”</strong></p><ul><li><strong>The Reality:</strong> False. Underexposure creates <em>more</em> noise, not silence. If you take a photo in the dark, the sensor struggles and generates static (read noise). These images don’t have static; they have empty data. That is the fingerprint of the “Black Point” slider in Photoshop, not a camera shutter.</li></ul><h3>Bottom Line</h3><blockquote><em>The argument is not that RAW images must start at a specific numeric value, but that active image data must statistically overlap with the contemporaneously measured optical black floor. A persistent empty band between those two domains violates known CMOS sensor behavior and is strong evidence of non native RAW payload insertion or reconstruction.</em></blockquote><p>— — — — — — —</p><h3><strong>FAQ for Journalists</strong></h3><h3>Q1. Are you claiming RAW images must start at value 1023 or 1024</h3><p>No. That is a strawman.</p><p>The metadata black level is a calibration offset, not the physical noise floor. The relevant reference point is the <strong>measured optical black</strong>, derived from masked sensor pixels at the time of capture.</p><h3>Q2. What is the optical black and why does it matter</h3><p>Masked optical black pixels are shielded from light and record only the sensor’s electronic behavior. They capture read noise, bias drift, and ADC characteristics for that specific frame. This makes them the most reliable reference for the true sensor floor during exposure.</p><h3>Q3. What should a genuine RAW file look like relative to optical black</h3><p>In a genuine capture, <strong>active image pixels statistically overlap with the measured optical black floor</strong>. Even in bright scenes, read noise ensures some active pixels fall near that floor. A clean empty gap is not expected.</p><h3>Q4. Why is a gap between optical black and image data suspicious</h3><p>Because it means low code values that must exist physically are missing. If masked pixels show values around 1070 but active pixels begin only at 1210 with zero population below, that violates known CMOS readout behavior.</p><h3>Q5. Could scene brightness explain the gap</h3><p>No. Scene brightness affects signal level, not read noise. Read noise exists regardless of scene content. Bright clouds do not eliminate low value pixel variance.</p><h3>Q6. Could noise reduction or RAW converters cause this</h3><p>No.</p><p>The analysis uses linear RAW data with processing disabled. Masked pixels are not demosaiced or denoised. Any operation that removed low values from active pixels would also affect masked pixels, which is not observed.</p><h3>Q7. Could in camera processing lift blacks only in active pixels</h3><p>No known camera pipeline does this. Black level offsets and clipping affect the entire frame uniformly. A separation between masked and active domains implies post capture manipulation.</p><h3>Q8. Doesn’t Canon or an expert saying the files are legitimate settle this</h3><p>No. Authority statements that do not address the <strong>measured optical black versus payload gap</strong> are irrelevant. Forensics is resolved by physical consistency, not by general assurances.</p><h3>Q9. Are histograms alone sufficient proof</h3><p>Histograms are not the proof; they are the visualization.</p><p>The proof is the <strong>absence of low code values that must exist given the measured sensor floor</strong>. The histogram simply makes that absence visible.</p><h3>Q10. Could this be a rare edge case</h3><p>Edge cases are random and inconsistent.</p><p>The same structured gap appears across multiple files with the same camera model, indicating a systematic process rather than stochastic sensor behavior.</p><h3>Q11. What does this anomaly most likely indicate</h3><p>A non native RAW payload, such as a reconstructed image inserted into a RAW container, or a processed image exported in a way that suppresses low level sensor noise while leaving masked pixels intact.</p><h3>Q12. What would falsify this claim</h3><p>Any genuine RAW file where:</p><ul><li>masked optical black is measured, and</li><li>active pixels show a normal overlapping tail down to that floor</li></ul><p>No such counterexample has been presented for the files in question.</p><h3>Q13. Why is Google Drive distribution a RED FLAG</h3><p>Mutable storage allows files to be replaced without version traceability. For forensic claims, stable hashes and immutable repositories are required.</p><h3>Q14. Is this argument dependent on one tool or viewer</h3><p>No. The gap persists across viewers when RAW linear data is inspected correctly with processing disabled.</p><h3>Final clarification</h3><p>This analysis does not rely on opinion, authority, or aesthetics. It relies on whether physical constraints of CMOS sensors are respected. In these files, they are not.</p><p>These are fabricated images, made by individual who’s capable of reverse engineering the CR2 file.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — -</p><h3>For the nerds</h3><p>— — — — — — — — — — — — — — — — — — — — —</p><p><strong>Critical distinction- Forensics vs Viewer</strong></p><blockquote>raw_rgb = raw.postprocess(no_auto_bright=True</blockquote><p>Here is why this specific flag is critical for any forensic analysis:</p><ol><li><strong>Viewer setting(</strong><strong>False):</strong> If you do <em>not</em> set this flag (or set it to False), rawpy behaves like a <strong>standard photo viewer</strong>. It looks at the histogram, sees that the image is dark, and automatically multiplies the pixel values to stretch them across the histogram so the image looks &quot;appealing&quot; to the human eye. Those desperate to hide image flaws want this to stay <strong>false</strong> so you can never guess it’s faked.</li></ol><ul><li><strong>Why? </strong>This stretching can hide the “gap” on the left side. It might pull the data down to 0 or push it up, masking the hard clipping you are trying to prove.</li></ul><p><strong>2. Forensic Setting (</strong><strong>True):</strong> By setting no_auto_bright=True, you are telling the processor: <em>&quot;Do not touch the math. If the pixel value is 10, leave it at 10. Do not scale it to 50 just to make it brighter.&quot;</em></p><ul><li><strong>Why? </strong>This ensures that if there is a gap of “0 pixels” in the first 50 levels, it remains visible as a gap. It creates a linear, <strong>scientific representation of the sensor data </strong>rather than an aesthetic one.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YZ198NIwRDvPdNrjbZkTiA.png" /><figcaption>Jonas Fake cloud image Hashes. So if the hashes change we know the scammers fixed their CR2s based on these findings.</figcaption></figure><p>More Histograms including Luminosity profiles (14 Bit) across real and Fake Jonas images</p><p><strong><em>Note:</em></strong><em> All Black levels are calcuated dynamically per shot, and not the 1023 floor/value inserted into the metadata</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zWvuGGNJpZh02GZ-5gNx4g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*4XFnafh5uutHk-_vcpTpGw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*3H6V0sbgkonIhrb5tV1ggA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*sEpvJicA1jwYv2d5SJltcw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*IcqruaWrLECg3zoXzgCPPg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*iAfXRdLUa_RkfybXUf89jA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*uza6BM63KzMtvPe2iJC-aw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*bDs0VSO5UaFJrZjLlcEzsw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Ke7ElbVVAlaNBYqlmQkp3g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*8N_zaDeFCd1CiXJtS5E-6g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*fyYZNtomQE4Ss7KelgtCkQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*fulnNfCcfRmTDZHWeO_3Ig.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*kCY7PxrnlrugREIm05g9ww.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*aGL3fSTpdqMUgZ4wdZ-D9g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*8bIFuGfA49VgfddHCa8D9Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*CGWaaMs8pQ0D0gjQ8ehiRg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*eHe1rYm31eU-J3USTT_C6g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*hZ083UWm28_W9Ub72Zscjg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*OIRd4gi4-vyktI1kxuQvtA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*ZI7d4YbSmprnxPyTFKv6sQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*ZI7d4YbSmprnxPyTFKv6sQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*kv3fuvk7a5zcF-0E9174zQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*19-n2TfBOn6MIBTxmcgV3A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Qr0rmLGc5iPDPYPgXq7Vwg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*u8c8tqxjzYVirrtaKfGQ-w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*9QQS0LX2IGwgsZnoi3X49A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*SYlWFI97MXI4yTYwz2piIg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*-wLKVuDvZ6ipUSwlB1o4LA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*aAA_1lAArsIdtkl7KRdOxw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*eh9JC9FPIk7NKQb2zHdo6A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*czxRIfmVGUG8VuEFqW0jbQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*OmgnGWl9RCZ8HRZLY4JanA.png" /></figure><h3>Sources:</h3><h3>1. Gardella et al. (2021)</h3><p><strong>Title:</strong> Forgery Detection in Digital Images by Multi-Scale Noise Estimation <strong>Link:</strong> <a href="https://www.mdpi.com/2313-433X/7/6/98">MDPI Open Access</a> <strong>DOI:</strong> 10.3390/jimaging7060098</p><h3>2. Lukáš, Fridrich, &amp; Goljan (2006)</h3><p><strong>Title:</strong> Determining Image Origin and Integrity Using Sensor Noise <strong>Link:</strong> <a href="https://www.google.com/search?q=https://ieeexplore.ieee.org/document/1634360">IEEE Xplore</a> (Alternative: <a href="https://www.google.com/search?q=https://www.researchgate.net/publication/3455364_Determining_Image_Origin_and_Integrity_Using_Sensor_Noise">ResearchGate Full-text</a>) <strong>DOI:</strong> 10.1109/TIFS.2006.873602</p><h3>3. Chen et al. (2018)</h3><p><strong>Title:</strong> Focus Manipulation Detection via Photometric Histogram Analysis <strong>Link:</strong> <a href="https://openaccess.thecvf.com/content_cvpr_2018/html/Chen_Focus_Manipulation_Detection_CVPR_2018_paper.html">CVF Open Access</a></p><h3>4. Popescu &amp; Farid (2005)</h3><p><strong>Title:</strong> Exposing Digital Forgeries by Detecting Traces of Resampling <strong>Link:</strong> <a href="https://www.google.com/search?q=https://ieeexplore.ieee.org/document/1384070">IEEE Xplore</a> (Alternative: <a href="https://www.google.com/search?q=https://www.cs.dartmouth.edu/farid/downloads/publications/tsp05.pdf">Dartmouth College Repository</a>) <strong>DOI:</strong> 10.1109/TSP.2004.839932</p><h3>5. Aubin et al. (2022)</h3><p><strong>Title:</strong> Probing Dark Current Distribution and Evolution in a CMOS Image Sensor <strong>Link:</strong> <a href="https://ieeexplore.ieee.org/document/9645220">IEEE Xplore</a> (Alternative: <a href="https://www.google.com/search?q=https://ntrs.nasa.gov/citations/20210023608">NASA Technical Reports Server</a>) <strong>DOI:</strong> 10.1109/TNS.2021.3134633</p><h3>6. Gardella M, Musé P. (2021)</h3><p><strong>Title:</strong> Gardella M, Musé P, Morel JM, Colom M. Forgery Detection in Digital Images by Multi-Scale Noise Estimation. J Imaging. 2021 Jul 17;7(7):119. doi: 10.3390/jimaging7070119. PMID: 39080907; PMCID: PMC8321373. <strong>Link</strong> <a href="https://pmc.ncbi.nlm.nih.gov/articles/PMC8321373/">https://pmc.ncbi.nlm.nih.gov/articles/PMC8321373/</a></p><h3>7. Voltage, Deadzone and Histogram to detect synthetic images (2023)</h3><p>Reed, A. (2023) “OPTICAL BLACK DECOUPLING AND GAUSSIAN STERILITY: PHYSICS-BASED FALSIFICATION OF SYNTHETIC RAW IMAGERY.”</p><h4><a href="https://clarkvision.com/reviews/evaluation-canon-5dii/index.html"><strong>8. </strong>https://clarkvision.com/reviews/evaluation-canon-5dii/index.html</a></h4><p><a href="https://pmc.ncbi.nlm.nih.gov/articles/PMC8321373/">Forgery Detection in Digital Images by Multi-Scale Noise Estimation</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e43104f522b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CR2 RAW spoofing, Photobashing and VFX]]></title>
            <link>https://medium.com/@Fastlane90/cr2-raw-spoofing-and-vfx-3f600171f8d6?source=rss-63141a9ae671------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f600171f8d6</guid>
            <category><![CDATA[canon]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[photography]]></category>
            <category><![CDATA[raw]]></category>
            <category><![CDATA[vfx-compositing]]></category>
            <dc:creator><![CDATA[CasualObserver]]></dc:creator>
            <pubDate>Wed, 24 Dec 2025 07:07:25 GMT</pubDate>
            <atom:updated>2025-12-24T19:56:06.738Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FvRpHMEIpg3rev_D7wEyyw.png" /><figcaption>Photobashing is a popular synthetic scene creation method.</figcaption></figure><h3>VFX Pipeline and the Role of RAW Data</h3><p>In professional VFX, “RAW” is the lifeblood of a <strong>linear workflow</strong>. Unlike JPEGs which have color and contrast “baked in,” RAW data preserves the <strong>unprocessed light response</strong> of the camera sensor. VFX artists require this because it provides the <strong>maximum dynamic range</strong> and bit depth (typically 14-bit or 16-bit) needed for high-end compositing. By working with linear data, artists can mathematically align CG lighting with the real-world exposure values of a live-action plate. If a CG explosion is ten times brighter than the sky, RAW data allows the compositor to “stop down” the exposure in post and see the highlights in both, whereas a non-RAW format would simply clip those values to pure white.</p><h3>The Era of CR2 Spoofing (2015–2018)</h3><p>Between <strong>2015 and 2018, spoofing CR2 headers was a standard practice by VFX and Photobashers,</strong> largely driven by DSLR hacking communities. During this period, cameras like the Canon 5D Mark II/III were pushed to perform functions they weren’t designed for.</p><p>To make professional editing software recognize these hacked and extracted <strong>“raw frames,” </strong>developers had to wrap the data in <strong>synthetic CR2 containers</strong>. This “identity theft” was necessary because most professional color-grading tools only had built-in support for established proprietary formats. Spoofing allowed <strong>VFX artists </strong>to bypass software restrictions and access high-end color science on consumer hardware.</p><h3>VFX Pipeline: Why RAW is Essential</h3><p>In professional VFX, RAW data is the foundation of a <strong>linear workflow</strong>. Unlike baked JPEGs, RAW preserves the sensor’s unprocessed light response, offering the 14-bit to 16-bit dynamic range required for seamless compositing. This allows artists to mathematically match CG lighting to real-world exposure values — ensuring that highlights aren’t clipped and that digital assets “sit” perfectly within a live-action plate.</p><h3>The Era of CR2 Spoofing (2014–2018)</h3><p>Before DNG became the open standard, spoofing CR2 headers was a common hack within the <strong>Magic Lantern</strong> community. To force professional software to recognize RAW video frames from “unauthorized” hardware like the Canon 5D Mark III, developers wrapped synthetic data in real CR2 containers. This “identity theft” allowed artists to access high-end color science on consumer gear until <strong>DNG and CinemaDNG</strong> provided a more flexible, open-source alternative.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6ZaTudPc0_aYtzQlk-tBdQ.png" /></figure><h3>From Photobashing to Forensic Forgery</h3><p>Creating a fake CR2 is the technical “reverse-engineering” of a <strong>photobashed</strong> composite — a technique where VFX artists blend 3D renders and photographic textures into a seamless scene.</p><p>To turn this art into a “forgery,” the flattened image is put through a <strong>Bayerization</strong> script that maps RGB colors back into a sensor-specific RGGB mosaic. This synthetic payload is then injected into a <strong>donor CR2 container</strong>, effectively “signing” the fake image with a real camera’s serial number and hardware metadata to bypass the skepticism usually reserved for JPEGs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p_nirZDmo_x04j3w-Lec1A.png" /><figcaption>A Photobashed Composite with layered synthetic noise</figcaption></figure><h3>The Transition to Fake CR2 Generation</h3><p>Once the VFX scene is flattened, it is a high-resolution template for a forensic forgery. To transform this edited image into a “RAW” file, forgers use scripts to “Bayerize” the pixels, mapping the RGB colors back into the specific RGGB mosaic pattern used by DSLR sensors. This synthetic mosaic is then injected into a <strong>donor CR2/CR3 container</strong>, effectively “signing” the fake image with the serial number and hardware metadata of a real camera.</p><p>This process is designed to bypass the common skepticism toward JPEGs, as the presence of a RAW file implies that the image is a direct, untouched “digital negative” straight from the sensor, even if the content inside was built in a VFX suite.</p><h4>Interested in learning ways to spoof/hack a RAW CR2?</h4><p><a href="https://medium.com/@Fastlane90/how-to-spoof-a-cr2-file-a0d3c11b0caf">How to spoof a CR2 File.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f600171f8d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>