No ownership or control links for Chen Yu are resolved in the current sources yet — view the network graph to expand, or pull the cited JSON dossier.

What is Chen Yu's risk level?

WhiteIntel flags Chen Yu as medium risk on 2 signals. Risk levels are heuristic investigative leads, not legal determinations of beneficial ownership.

Where does Chen Yu appear across sources?

Chen Yu is resolved across ICIJ Offshore Leaks, OpenOwnership, opensanctions_pep into one cited cluster in the WhiteIntel corporate-ownership graph, with a source on every claim.

LIVE · CORPUS

Coverage — measured

Sources fused: 1
Resolved records: 10

An absent edge means not yet observed — never does not exist.

PersonMedium

Chen Yu

Name: Chen Yu — ownership dossier
Creator: WhiteIntel
License: https://whiteintel.dev/terms
Keywords: corporate ownership, beneficial ownership, UBO, corporate intelligence, OSINT, corporate registry, Chen Yu, Person, CN

Chen Yu — Chinese person. 2 sanctions/PEP signals. Cited to 1 registry.

born 1996 · 3 sources

Ownership graph Export .md

JSON / MCPsample

Politically exposed person

Politically exposed: a screening signal for enhanced due diligence, not a finding of wrongdoing.

Named in 5 ICIJ Offshore Leaks records — the Panama, Paradise & Pandora Papers.

Investigative lead by resolved identity, not a legal determination.

/01

Registry identity

Born: 1996
Appears in: 3 sources
Risk: Medium
Jurisdiction: CN
Flags: PEP

/02

Politically exposed person

PEP

MediumPolitically Exposed Personvia resolved record

Source list

A PEP designation calls for enhanced due diligence — it is an investigative lead, not an allegation of wrongdoing.

/03

Offshore leaks

ICIJ — Panama · Paradise · Pandora

This entity is named in 5 records in the ICIJ Offshore Leaks Database — the Panama, Paradise and Pandora Papers and the Offshore Leaks investigations.

Appearing in the ICIJ data is not evidence of wrongdoing — offshore entities have many legitimate uses. Source: ICIJ Offshore Leaks Database (offshoreleaks.icij.org), surfaced as derived links with attribution under its share-alike terms, never rehosted.

/04

Also appears in

OpenOwnership · opensanctions_pep

The same real-world entity, resolved across sources.

/05

Control & directorships

No ownership or control links resolved yet

An absent link means “not yet observed in our current sources”, not that none exists — cross-source resolution is still growing.

Watch this entity

We flag the moment ownership, a filing or a sanctions signal lands on it — the fastest way to catch a change on a subject we hold little on today.

Where we look Report a lead Expand in the graph

WHAT YOU CAN SEEFREE

YOURS NOW · FREE

4 items you can read right now — no account, no payment.

Identity, nationality & aliases
Sanctions, PEP & watchlist detail
Direct connections (1 hop)
Community notes

Nothing further on Chen Yu is behind a paywall — everything we hold on this subject is already on this page.

/06

Sanctions & PEP screening

Name match — unverified

2 watchlist records share this exact name. These are possible matches by name only — not confirmed as the same person. Verify identity (date of birth, nationality, ID) before relying on this.

/07

Common questions

Who owns Chen Yu?: No ownership or control links for Chen Yu are resolved in the current sources yet — view the network graph to expand, or pull the cited JSON dossier.
What is Chen Yu's risk level?: WhiteIntel flags Chen Yu as medium risk on 2 signals. Risk levels are heuristic investigative leads, not legal determinations of beneficial ownership.
Where does Chen Yu appear across sources?: Chen Yu is resolved across ICIJ Offshore Leaks, OpenOwnership, opensanctions_pep into one cited cluster in the WhiteIntel corporate-ownership graph, with a source on every claim.

Community intel

Crowd leads · unverified

Tips, corrections and leads contributed by the community on Chen Yu. These are unverified leads, not WhiteIntel findings — we surface them for investigators to chase, and analyse the corroborated ones into SnitchScore.

Loading tips…