Back to blog

Fake Chevron "Group CEO" on LinkedIn: How Do You Verify a Counterparty Claiming Oil Major Executive Authority?

Fake Chevron Group CEO LinkedIn claim: how to verify oil major executive identity against 10-K filings before OFAC SDN screening. FATF Rec 10 protocol.

August 1, 2026By OilFlow Intelligence8 min readscam_pattern_teardown

Screening a specific counterparty? Full 7-step dossier — $25, no account, report by email within the hour.

Fake Chevron "Group CEO" on LinkedIn: how do you verify a counterparty claiming oil major executive authority?

You verify against issuer-controlled sources, never against the profile itself. Chevron's chief executive officer is Mike Wirth, in role since February 2018, preceded by John Watson from 2010 to 2018 and Dave O'Reilly from 2000 to 2010, all documented in Chevron's SEC Form 10-K filings and on the company's own leadership page. A LinkedIn profile at linkedin.com/in/simar-chahal-02461526/, reviewed via operator-supplied screenshots on 28 May 2026, claims employment as Chevron "Group Chief Executive Officer" since August 2002. That is a claim mismatch a compliance officer can resolve in under sixty seconds, and under FATF Recommendation 10 the verification of any natural person purporting to act on behalf of a customer is customer due diligence, not an HR curiosity.

The artifact, and only the artifact

We are reporting one verified thing. A public LinkedIn profile asserts a current employment relationship with Chevron in the most senior executive role the company has, with a start date of August 2002.

The public record does not support it. In August 2002, Chevron's chief executive was Dave O'Reilly. The role passed to John Watson in 2010 and to Mike Wirth in February 2018. The lineage is disclosed in Chevron's annual 10-K filings and restated on chevron.com. Two sources, both controlled by the issuer, both free, both indexed.

We make no allegation about the account holder's conduct, intent, or communications. We have not observed a cargo, a charter, an invoice, or an approach attributable to this profile, and we are not asserting one. What we have is a documented, dated, screenshot-preserved employment claim that fails verification against the issuer's own disclosures. In a screening file, that is a finding in its own right. Treat it as such.

Timeline arithmetic is the cheapest tell you own

Executive-identity claims fail most often on dates, not on names. Fabricated or inflated profiles tend to pick a role and back-date the tenure to manufacture gravitas, because a two-decade run at the top of a supermajor reads as unimpeachable to a first-line sales desk under quota pressure.

The problem for the fabricator is that public-company CEO succession is one of the most heavily documented facts in corporate life. It appears in 10-K and 10-Q filings, proxy statements, 8-K announcements of appointment, and press releases. It is not contested, it is not paywalled, and it does not require a subscription database.

So the check is arithmetic. Take the claimed start date. Take the issuer's disclosed succession record. If the claimed tenure overlaps a period when a different named individual held the office, the claim is false on its face. There is no benign interpretation that survives, because a company does not have two Group CEOs at once. This one test, applied at first contact, kills a large share of impersonation attempts before any commercial document is exchanged.

Executive impersonation sits upstream of every sanctions check

Here is the structural point for MLROs. Sanctions screening is name-matching against lists. The OFAC SDN List, the UK OFSI consolidated list, and the EU consolidated list all work the same way: you submit a name, you get a hit or you get a clear.

That architecture has an unavoidable dependency. It presumes the name you submit is the name of the party you are actually dealing with.

An impersonated executive identity attacks the input, not the algorithm. If the profile at the head of your mandate chain claims to be a supermajor officer, and your screening engine dutifully clears "Chevron" as a counterparty, you have not screened your counterparty. You have screened a company that is not in the transaction. The clear result is real, the reassurance is not.

This is why identity verification is upstream of list screening in FATF Recommendation 10 and in every risk-based framework built on it. Recommendation 10 requires identifying the customer, verifying that identity using reliable, independent source documents, and, where a person purports to act on behalf of a customer, verifying that person's authority to do so. A LinkedIn profile is neither reliable nor independent. It is self-attested, self-edited, and deletable by the subject at any moment.

Why dark-fleet screening that stops at the hull is half a screen

The dark fleet discipline has matured fast. Desks now check IMO numbers, AIS gap history, flag hopping, ship-to-ship transfer patterns, P&I cover status, and prior designation of the registered and beneficial owner. That work is necessary and it is good.

It is also downstream. A vessel enters the file after somebody has agreed to a cargo, a price, a delivery window, and a payment instrument. That agreement is signed by people. If the people are unverified, the vessel screen is a control applied to a transaction whose origin was never established.

The generic mechanism, described without attribution to any named party, runs like this. A claimed senior identity at a recognised international oil company supplies apparent authority at the top of the mandate chain. Below it sit intermediary entities with plausible corporate names, incorporation details that are difficult to confirm, and a mandate letter or authorisation that references the executive above them. Documentation flows in familiar formats: an ICPO, an LOI, a soft corporate offer, then a request for a DLC MT700 or a partial advance against inspection. Product is usually a liquid, easily priced grade, EN590 diesel, RON 95 gasoline, jet A-1, or naphtha, because a real market price makes the discount feel legible.

Each added intermediary is a layer in the layer cake. The purpose of the layer cake is not complexity for its own sake. It is to place distance between the counterparty you believe you have and the party who actually receives funds or nominates tonnage. The executive impersonation is the top layer, and it is the cheapest one to build. A profile costs nothing. A vessel costs money.

Verification sequence: issuer-controlled sources only

A workable first-contact protocol, in order:

  1. Issuer leadership page. Named officers, current roles. Chevron publishes this at chevron.com/about/leadership. Every listed major does the equivalent.
  2. SEC filings, or the home-market equivalent. The 10-K names executive officers. An 8-K announces appointments and departures with dates. For non-US issuers, use the annual report and regulatory news service filings.
  3. Company switchboard, dialled from the number on the issuer's own site. Never from a number in the counterparty's signature block or email footer.
  4. Domain provenance on the email address. Free-mail addresses and lookalike domains claiming supermajor employment are disqualifying on their own.
  5. Authority to bind. Even where a person is genuinely employed, verify that the specific role carries authority for the specific transaction. Recommendation 10 asks for authority, not just identity.
  6. Then, and only then, run list screening. OFAC SDN, OFSI, EU consolidated, plus vessel and owner checks on any nominated tonnage.

Nothing in that sequence requires a vendor. It requires the discipline to treat the identity layer as a control point rather than a formality.

Preserve the artifact before it is edited

Profiles change. Employment entries are edited, dates are adjusted, accounts are deleted. If your desk finds a claim mismatch, the evidentiary window may be short.

Capture a full-page screenshot including the profile URL and the system date. Record the reviewer and the review date, as we did here with the 28 May 2026 review. Preserve the URL slug, which persists across display-name changes. File it against the counterparty record, not in an analyst's inbox. If the matter later becomes a SAR, an internal escalation, or a fraud referral, the contemporaneous artifact is the difference between a documented finding and a recollection.

Market conditions do not create these approaches, but they set the tempo. On the 31 July 2026 brief, with four of five price sources reporting, Brent stood at $90.12, up $1.09, WTI at $86.80, up $3.21, and Dubai at $88.12. Firm flat price means active deal flow, and active deal flow is precisely when unverified mandates arrive claiming urgency.

What compliance teams should do

  • Move executive-identity verification into first-line onboarding. It belongs before sanctions screening in the workflow, because it determines whose name you screen.
  • Apply the tenure-overlap test at first contact. Compare any claimed executive tenure against the issuer's disclosed succession record in filings. Overlap with a different named officer is a hard fail, no exceptions, no benefit of the doubt.
  • Ban self-attested sources from the verification file. LinkedIn, personal websites, and counterparty-supplied PDFs are leads, not evidence. Issuer IR pages and regulatory filings are evidence.
  • Verify authority to bind separately from identity. FATF Recommendation 10 requires both where a person acts on behalf of a customer.
  • Screen the mandate chain, not just the named principal. Every intermediary between the claimed executive and the payment instrument is a layer. Identify who receives funds and who nominates tonnage.
  • Log and timestamp every claim mismatch. Screenshot, URL, reviewer, date. File against the counterparty record before the profile changes.
  • Escalate to the MLRO on identity failure alone. A counterparty whose stated identity fails verification is a red flag independent of whether any transaction proceeded.
  • Extend dark fleet screening backwards. Hull-level checks stay, and a people-level check goes in front of them. Screening tankers but not the people signing for them is screening half the transaction.

OilFlow Intelligence builds counterparty files that start at the identity layer and run through to vessel and payment routing. To see how a claim mismatch like this one enters a screening record, request a walkthrough, or subscribe to the desk brief for typology teardowns as they are documented.

Evidence basis: LinkedIn profile screenshots supplied by operator, reviewed 28 May 2026; Chevron SEC Form 10-K filings and chevron.com/about/leadership. This article records a documented claim mismatch. It makes no allegation of criminal conduct, contact, or transaction activity by any named individual.

Verified trade-fraud patterns, sanctions deltas, and regulator actions. Weekly, for compliance and risk teams.

Double opt-in. No spam. The quarterly Compliance Index ships to subscribers first.

This article is part of our scam-cluster intelligence series. Screening a specific counterparty? Run the free check, or order the full 7-step dossier.