The Simar Chahal Cluster: Chevron-CEO Impersonation

Between 2026-05-25 and 2026-05-28, three cargo-scale physical-commodity pitches routed through a single buyer-side origin: a LinkedIn profile naming "Simar Chahal" as Chevron's Group Chief Executive Officer since August 2002. Chevron's actual Group CEO has been Mike Wirth since February 2018; prior to that John Watson held the role from 2010 to 2018, and Dave O'Reilly from 2000 to 2010. Each tenure is publicly documented in Chevron's 10-K SEC filings and on chevron.com/about/leadership. Simar Chahal has never held that role. The impersonation is independently verifiable.

The pitches collapsed not because the cargo specs were wrong — they were carefully constructed — but because the buyer's claimed employment did not survive a one-minute check against the public record. The pattern matters because it is now a repeatable typology: a falsified executive identity at a household-name producer, layered over a chain of fabricated counterparties (one of them named after a desert planet from a 1965 novel).

The LinkedIn profile (linkedin.com/in/simar-chahal-02461526/) claims employment as Chevron's "Group Chief Executive Officer" beginning August 2002. Chevron's SEC filings list a different person in that role for every year in the claimed tenure:

The profile contains an internal contradiction that is visible without any external verification: the headline reads "Chevron Dealer + Group Head at SSW Kafcima", while the Experience block lists "Group Chief Executive Officer at Chevron". These are mutually exclusive roles — a person is not simultaneously a Chevron dealer and Chevron's CEO. The contradiction is the kind of signal a compliance team should never have to chase manually; it is detected by string-comparison in OilFlow's automated cluster sweep.

The Experience block names two entities Simar "primarily trades with": Arrakis Development and Exxon Global Distributor. Arrakis is the fictional desert planet from Frank Herbert's 1965 novel Dune. Exxon Global Distributor is not a registered ExxonMobil entity — the real ExxonMobil trading and distribution subsidiaries are ExxonMobil Supply Company, ExxonMobil Asia Pacific, ExxonMobil Sales & Supply, and ExxonMobil Petroleum & Chemical.

The claimed employer — SSW Kafcima — does not appear in any International Oil Company, National Oil Company, trading-house, or refinery ecosystem map, and is not a documented Chevron trading counterparty. The phrase "Group Head" appears without a function (Group Head of what?), which is characteristic mandate-chain word salad.

Migration 117 of the OilFlow schema added the following rows to broker_scam_blocklist. Any inbound match through /api/v1/clusters/check returns the row including evidence JSON.

Every entity in this cluster lives in broker_scam_blocklistwith the evidence JSON intact. Any of the following inbound calls will return a cluster match within sub-second latency:

• ·
  GET /api/v1/clusters/check?entity=Simar%20Chahal

  Returns the confirmed-fraud row with the full LinkedIn evidence chain.

• ·
  POST /api/v1/predeal/check

  An RM pasting a Simar-sourced cargo description gets a block verdict with a clearance probability under 5 % in under 30 seconds.

• ·
  GET /api/v1/predeal/pulse/Simar%20Chahal

  Returns the full 60-second counterparty pulse: cluster hit + adverse media + sanctions check + Pre-Deal history.

The Simar cluster is one instance of a typology that is now actively re-used across the EM broker ecosystem:

1. Falsified executive identity at a household-name producer (Chevron / ExxonMobil / Shell / Saudi Aramco), supported by a LinkedIn profile that survives only as long as the reader doesn't check the actual CEO history.
2. Fictional counterparty stack named at plausible-looking employer or partner entities that do not exist in any corporate registry, IOC/NOC ecosystem map, or trading-house publication.
3. Internal profile contradiction where the headline and the experience section claim mutually exclusive executive roles at the same producer, visible to anyone who reads the full profile.
4. Cargo-scale specificity (named volumes, named destinations, named payment terms) that survives a casual read because the spec was constructed correctly even though the principal is fabricated.

A compliance team relying on sanctions-list screening alone will never catch this typology — none of these entities are on any OFAC, UN, EU, or HMT list. They are caught only by first-party investigated cluster intelligence with the routing-layer mapped.

This cluster was not aggregated from a vendor feed. The buyer pitch came in to the operator directly through a Pakistan-based broker network. The screenshots of the LinkedIn profile are timestamped and archived in OilFlow's investigation file. The Chevron CEO comparison was performed against publicly accessible Chevron 10-K filings and the company's leadership page. The fictional-entity verifications attempted Bloomberg, Reuters Eikon, S&P Platts, Singapore ACRA, and Chevron 10-K disclosed JV lists.

Cluster intelligence is only useful at audit-trail quality when the evidence chain travels with the record. Every row in OilFlow's blocklist carries the originating source, the investigator, and the jsonb evidence bundle. Examiners and regulators can be shown the full provenance behind any blocked decision.