Ryuhei Matsuda

Also reported as: ryuhei.ethryuheimatryuheimat3akame.eth0xhiros

A professional identity listed by a third-party registry of suspected DPRK IT-worker personas, cited below. The registry publishes no byline or methodology, so the attribution is the registry's. Values this site read from a live account are cited to the page and date.

IT Worker Fraud First reported 2026-08-30 · last reported 2026-10-18

Profiles and evidence

LinkedIn accounts

Identifiers reported alongside

17 indicators filed under the same heading, each with its sources.

IndicatorTypeAccount status
akame.eth alias —
Ryuhei Matsuda alias —
ryuhei.eth alias —
https://hub.docker.com/u/ryuheimat dockerhub account live checked 2026-11-08
ryuheimat3@gmail.com email address —
https://github.com/jcking89 github profile live checked 2026-09-30
https://github.com/mono300genuine github profile live checked 2026-08-30
https://github.com/ryuheimat github profile live checked 2026-08-30
https://gitlab.com/ryuheimat gitlab account not checked
https://gitlab.com/ryuheimat3 gitlab account not checked
https://keybase.io/ryuheimat keybase account live checked 2026-11-08
https://medium.com/@ivan.shodanov medium account not checked
0x36c67d5ce9e2e4a919f568fc33657fcad0030880 wallet address —
0x6fb678b2dd9d2ff50ee9ecf774251dcceb7a2da8 wallet address —
0x86fce1a6cbaaf0d0d7cb727e9b9eac5ed4150a5b wallet address —
0xa71b641a498e33bb13548a01eca5e20e083e637b wallet address —
0xd97729eef14c189144adb0591e4ddb1a66ce22af wallet address —

akame.eth

alias IT Worker Fraud THIRD-PARTY REGISTRY

First seen unknown · last seen unknown

Source

  • Entry in the lazarus.group DPRK IT-worker registry, which asserts that these accounts belong to one operator. The registry publishes no methodology, so this is recorded as its claim and not as a finding of this site. Its evidence links and its cross-references to other operators in the same registry are deliberately not reproduced as indicators.
    lazarus.group/team/ryuhei-matsuda — Lazarus Group DPRK IT-Worker Registry (lazarus.group) · under “Ryuhei Matsuda / ryuhei.eth / ryuheimat / ryuheimat3 / akame.eth / 0xhiros” · pulled 2026-09-09

Ryuhei Matsuda

alias IT Worker Fraud CURATED

First seen 2026-09-24 · last seen 2026-09-24

Sources

  • Entry in the lazarus.group DPRK IT-worker registry, which asserts that these accounts belong to one operator. The registry publishes no methodology, so this is recorded as its claim and not as a finding of this site. Its evidence links and its cross-references to other operators in the same registry are deliberately not reproduced as indicators.
    lazarus.group/team/ryuhei-matsuda — Lazarus Group DPRK IT-Worker Registry (lazarus.group) · under “Ryuhei Matsuda / ryuhei.eth / ryuheimat / ryuheimat3 / akame.eth / 0xhiros” · pulled 2026-09-09
  • Found on 13 September 2026 by probing every account handle this site already holds for this operator against GitLab, and read from the profile cited. An active GitLab account exists under ryuheimat, a login the index already carries for this persona on another platform. The profile gives a member-since date of 11 September 2018. It displays the name Ryuhei Matsuda, the same name the reporting already gives. The handle is what links this account to the rest; nothing here establishes that one person holds both, and a display name on a profile is a name the account presents, not an identification. The profile's bio, location and links render only in a browser and were not read, so nothing is claimed about them either way.
    gitlab.com/ryuheimat — Chollima Hunter · under “Ryuhei Matsuda” · pulled 2026-09-13
  • Found on 17 September 2026 by asking Keybase whether an account exists under ryuheimat, one of the logins the registry already holds for this operator, and read from the profile cited. The account states a registration date of 17 May 2022 and no display name but the handle itself. The handle is what links this account to the rest; nothing here establishes that one person holds both, and a display name on a profile is a name the account presents, not an identification.
    keybase.io/ryuheimat — Chollima Hunter · under “Ryuhei Matsuda” · pulled 2026-09-17
  • Found on 17 September 2026 by asking Docker Hub whether an account exists under ryuheimat, one of the logins the registry already holds for this operator, and read from the profile cited. The account states a registration date of 11 July 2018. The handle is what links this account to the rest; nothing here establishes that one person holds both, and a display name on a profile is a name the account presents, not an identification.
    hub.docker.com/u/ryuheimat — Chollima Hunter · under “Ryuhei Matsuda” · pulled 2026-09-17
  • Found on 18 September 2026 by taking the local part of an address this index already holds for this operator -- ryuheimat3 -- and asking GitLab whether an account exists under it. The address is on a consumer mail host, where the local part is a login the holder chose rather than one an employer assigned; handles taken from company addresses were excluded from this pass for that reason. The account states a display name of Ryuhei Matsuda. The display name is kept here rather than carried as an alias, because it restates the handle, describes the work, or is too bare to be a name. The login is what links this account to the rest; nothing here establishes that one person holds both, and a display name on a profile is a name the account presents, not an identification.
    gitlab.com/ryuheimat3 — Chollima Hunter · under “Ryuhei Matsuda” · pulled 2026-09-18
  • Found on 24 September 2026 by searching GitHub's commit index for every personal address the lazarus.group registry gives for a persona, and keeping the accounts whose own repositories are committed with one. GitHub mints a noreply address from an account's immutable numeric id, in the form id+handle@users.noreply.github.com, so former handles below are a matter of record. github.com/jcking89 is account id 40835770, created on 4 July 2018, with 89 public repositories. Forty-nine commits in nineteen of them are signed ryuheimat3@gmail.com, an address lazarus.group and tayvano give for Ryuhei Matsuda, which GitHub attributes to github.com/ryuheimat, the account both list for the persona. They carry the author names ryuheimat, Ryuhei Matsuda, ryuhei and r2moon and are made on the day each repository was created, from cryptoExchange on 6 January 2021 and LendBorrow on 3 June 2021 to simple-univ3-integration on 6 July 2023; in all but one of the repositories read they are the only commits. An account whose repositories are opened with the persona's identity, over two and a half years, is the persona's second account or one it has push access to.
    github.com/jcking89 — Chollima Hunter · under “Ryuhei Matsuda” · pulled 2026-09-24

ryuhei.eth

alias IT Worker Fraud THIRD-PARTY REGISTRY

First seen unknown · last seen unknown

Source

  • Entry in the lazarus.group DPRK IT-worker registry, which asserts that these accounts belong to one operator. The registry publishes no methodology, so this is recorded as its claim and not as a finding of this site. Its evidence links and its cross-references to other operators in the same registry are deliberately not reproduced as indicators.
    lazarus.group/team/ryuhei-matsuda — Lazarus Group DPRK IT-Worker Registry (lazarus.group) · under “Ryuhei Matsuda / ryuhei.eth / ryuheimat / ryuheimat3 / akame.eth / 0xhiros” · pulled 2026-09-09

https://hub.docker.com/u/ryuheimat

dockerhub account IT Worker Fraud CURATED live checked 2026-11-08

First seen unknown · last seen unknown

Source

  • Found on 17 September 2026 by asking Docker Hub whether an account exists under ryuheimat, one of the logins the registry already holds for this operator, and read from the profile cited. The account states a registration date of 11 July 2018. The handle is what links this account to the rest; nothing here establishes that one person holds both, and a display name on a profile is a name the account presents, not an identification.
    hub.docker.com/u/ryuheimat — Chollima Hunter · under “Ryuhei Matsuda” · pulled 2026-09-17

ryuheimat3@gmail.com

email address IT Worker Fraud CURATED

First seen 2026-08-30 · last seen 2026-10-18

Sources

  • Entry in the lazarus.group DPRK IT-worker registry, which asserts that these accounts belong to one operator. The registry publishes no methodology, so this is recorded as its claim and not as a finding of this site. Its evidence links and its cross-references to other operators in the same registry are deliberately not reproduced as indicators.
    lazarus.group/team/ryuhei-matsuda — Lazarus Group DPRK IT-Worker Registry (lazarus.group) · under “Ryuhei Matsuda / ryuhei.eth / ryuheimat / ryuheimat3 / akame.eth / 0xhiros” · pulled 2026-09-09
  • Found on 24 September 2026 by searching GitHub's commit index for every personal address the lazarus.group registry gives for a persona, and keeping the accounts whose own repositories are committed with one. GitHub mints a noreply address from an account's immutable numeric id, in the form id+handle@users.noreply.github.com, so former handles below are a matter of record. github.com/jcking89 is account id 40835770, created on 4 July 2018, with 89 public repositories. Forty-nine commits in nineteen of them are signed ryuheimat3@gmail.com, an address lazarus.group and tayvano give for Ryuhei Matsuda, which GitHub attributes to github.com/ryuheimat, the account both list for the persona. They carry the author names ryuheimat, Ryuhei Matsuda, ryuhei and r2moon and are made on the day each repository was created, from cryptoExchange on 6 January 2021 and LendBorrow on 3 June 2021 to simple-univ3-integration on 6 July 2023; in all but one of the repositories read they are the only commits. An account whose repositories are opened with the persona's identity, over two and a half years, is the persona's second account or one it has push access to.
    github.com/jcking89 — Chollima Hunter · under “Ryuhei Matsuda” · pulled 2026-09-24
  • …Loom Network, Naos Finance, Raze Network, Sandclock, Shardeum, Paid Network, Hyperionx - ryuhei.eth - ryuheimat - ryuheimat3 - ryuheimat3@gmail.com - linkedin.com/in/ryuhei-matsuda - github.com/ryuheimat • [Archive](https://archive.ph/V5GsZ) - github.com/mono300genuine •…
    DPRK IT Workers — tayvano (lazarus-bluenoroff-research) · under “Ryuhei Matsuda” · published 2025-06-19 · pulled 2026-08-30

https://github.com/jcking89

github profile IT Worker Fraud CURATED live checked 2026-09-30

First seen 2026-09-24 · last seen 2026-09-24

Source

  • Found on 24 September 2026 by searching GitHub's commit index for every personal address the lazarus.group registry gives for a persona, and keeping the accounts whose own repositories are committed with one. GitHub mints a noreply address from an account's immutable numeric id, in the form id+handle@users.noreply.github.com, so former handles below are a matter of record. github.com/jcking89 is account id 40835770, created on 4 July 2018, with 89 public repositories. Forty-nine commits in nineteen of them are signed ryuheimat3@gmail.com, an address lazarus.group and tayvano give for Ryuhei Matsuda, which GitHub attributes to github.com/ryuheimat, the account both list for the persona. They carry the author names ryuheimat, Ryuhei Matsuda, ryuhei and r2moon and are made on the day each repository was created, from cryptoExchange on 6 January 2021 and LendBorrow on 3 June 2021 to simple-univ3-integration on 6 July 2023; in all but one of the repositories read they are the only commits. An account whose repositories are opened with the persona's identity, over two and a half years, is the persona's second account or one it has push access to.
    github.com/jcking89 — Chollima Hunter · under “Ryuhei Matsuda” · pulled 2026-09-24

https://github.com/mono300genuine

github profile IT Worker Fraud MATCHED IN SOURCE live checked 2026-08-30

Listed as mono300genuine

First seen 2026-08-30 · last seen 2026-10-18

Source

  • Nearby text:

    …ryuheimat3 - ryuheimat3@gmail.com - linkedin.com/in/ryuhei-matsuda - github.com/ryuheimat • [Archive](https://archive.ph/V5GsZ) - github.com/mono300genuine • [Archive](https://archive.ph/wip/Am9Cr) - 0x36c67d5ce9e2e4a919f568fc33657fcad0030880 (T) - 0x6fb678b2dd9d2ff50ee9ecf774251dcceb7a2da8…
    DPRK IT Workers — tayvano (lazarus-bluenoroff-research) · under “Ryuhei Matsuda” · published 2025-06-19 · pulled 2026-08-30

https://github.com/ryuheimat

github profile IT Worker Fraud MATCHED IN SOURCE live checked 2026-08-30

Listed as ryuheimat

First seen 2026-08-30 · last seen 2026-10-18

Sources

  • Entry in the lazarus.group DPRK IT-worker registry, which asserts that these accounts belong to one operator. The registry publishes no methodology, so this is recorded as its claim and not as a finding of this site. Its evidence links and its cross-references to other operators in the same registry are deliberately not reproduced as indicators.
    lazarus.group/team/ryuhei-matsuda — Lazarus Group DPRK IT-Worker Registry (lazarus.group) · under “Ryuhei Matsuda / ryuhei.eth / ryuheimat / ryuheimat3 / akame.eth / 0xhiros” · pulled 2026-09-09
  • Nearby text:

    …Shardeum, Paid Network, Hyperionx - ryuhei.eth - ryuheimat - ryuheimat3 - ryuheimat3@gmail.com - linkedin.com/in/ryuhei-matsuda - github.com/ryuheimat • [Archive](https://archive.ph/V5GsZ) - github.com/mono300genuine • [Archive](https://archive.ph/wip/Am9Cr) -…
    DPRK IT Workers — tayvano (lazarus-bluenoroff-research) · under “Ryuhei Matsuda” · published 2025-06-19 · pulled 2026-08-30

https://gitlab.com/ryuheimat

gitlab account IT Worker Fraud CURATED

First seen unknown · last seen unknown

Source

  • Found on 13 September 2026 by probing every account handle this site already holds for this operator against GitLab, and read from the profile cited. An active GitLab account exists under ryuheimat, a login the index already carries for this persona on another platform. The profile gives a member-since date of 11 September 2018. It displays the name Ryuhei Matsuda, the same name the reporting already gives. The handle is what links this account to the rest; nothing here establishes that one person holds both, and a display name on a profile is a name the account presents, not an identification. The profile's bio, location and links render only in a browser and were not read, so nothing is claimed about them either way.
    gitlab.com/ryuheimat — Chollima Hunter · under “Ryuhei Matsuda” · pulled 2026-09-13

https://gitlab.com/ryuheimat3

gitlab account IT Worker Fraud CURATED

First seen unknown · last seen unknown

Source

  • Found on 18 September 2026 by taking the local part of an address this index already holds for this operator -- ryuheimat3 -- and asking GitLab whether an account exists under it. The address is on a consumer mail host, where the local part is a login the holder chose rather than one an employer assigned; handles taken from company addresses were excluded from this pass for that reason. The account states a display name of Ryuhei Matsuda. The display name is kept here rather than carried as an alias, because it restates the handle, describes the work, or is too bare to be a name. The login is what links this account to the rest; nothing here establishes that one person holds both, and a display name on a profile is a name the account presents, not an identification.
    gitlab.com/ryuheimat3 — Chollima Hunter · under “Ryuhei Matsuda” · pulled 2026-09-18

https://keybase.io/ryuheimat

keybase account IT Worker Fraud CURATED live checked 2026-11-08

First seen unknown · last seen unknown

Source

  • Found on 17 September 2026 by asking Keybase whether an account exists under ryuheimat, one of the logins the registry already holds for this operator, and read from the profile cited. The account states a registration date of 17 May 2022 and no display name but the handle itself. The handle is what links this account to the rest; nothing here establishes that one person holds both, and a display name on a profile is a name the account presents, not an identification.
    keybase.io/ryuheimat — Chollima Hunter · under “Ryuhei Matsuda” · pulled 2026-09-17

https://medium.com/@ivan.shodanov

medium account IT Worker Fraud MATCHED IN SOURCE

Listed as @ivan.shodanov

First seen 2026-09-01 · last seen 2026-10-18

Source

  • Nearby text:

    …- https://icoholder.com/en/kira-1003837 - https://kylinnetwork.medium.com/kylin-network-monthly-report-2-d9b6be5b8cdf - https://medium.com/@ivan.shodanov/the-15-most-promising-small-cap-defi-projects-to-invest-in-2021-6e9d5aa5774c - https://polkastarter.com/projects/naos-finance -…
    DPRK IT Workers — tayvano (lazarus-bluenoroff-research) · under “Ryuhei Matsuda” · published 2025-06-19 · pulled 2026-09-01

0x36c67d5ce9e2e4a919f568fc33657fcad0030880

wallet address IT Worker Fraud THIRD-PARTY REGISTRY

First seen unknown · last seen unknown

Source

  • Entry in the lazarus.group DPRK IT-worker registry, which asserts that these accounts belong to one operator. The registry publishes no methodology, so this is recorded as its claim and not as a finding of this site. Its evidence links and its cross-references to other operators in the same registry are deliberately not reproduced as indicators.
    lazarus.group/team/ryuhei-matsuda — Lazarus Group DPRK IT-Worker Registry (lazarus.group) · under “Ryuhei Matsuda / ryuhei.eth / ryuheimat / ryuheimat3 / akame.eth / 0xhiros” · pulled 2026-09-09

0x6fb678b2dd9d2ff50ee9ecf774251dcceb7a2da8

wallet address IT Worker Fraud THIRD-PARTY REGISTRY

First seen unknown · last seen unknown

Source

  • Entry in the lazarus.group DPRK IT-worker registry, which asserts that these accounts belong to one operator. The registry publishes no methodology, so this is recorded as its claim and not as a finding of this site. Its evidence links and its cross-references to other operators in the same registry are deliberately not reproduced as indicators.
    lazarus.group/team/ryuhei-matsuda — Lazarus Group DPRK IT-Worker Registry (lazarus.group) · under “Ryuhei Matsuda / ryuhei.eth / ryuheimat / ryuheimat3 / akame.eth / 0xhiros” · pulled 2026-09-09

0x86fce1a6cbaaf0d0d7cb727e9b9eac5ed4150a5b

wallet address IT Worker Fraud THIRD-PARTY REGISTRY

First seen unknown · last seen unknown

Source

  • Entry in the lazarus.group DPRK IT-worker registry, which asserts that these accounts belong to one operator. The registry publishes no methodology, so this is recorded as its claim and not as a finding of this site. Its evidence links and its cross-references to other operators in the same registry are deliberately not reproduced as indicators.
    lazarus.group/team/ryuhei-matsuda — Lazarus Group DPRK IT-Worker Registry (lazarus.group) · under “Ryuhei Matsuda / ryuhei.eth / ryuheimat / ryuheimat3 / akame.eth / 0xhiros” · pulled 2026-09-09

0xa71b641a498e33bb13548a01eca5e20e083e637b

wallet address IT Worker Fraud THIRD-PARTY REGISTRY

First seen unknown · last seen unknown

Source

  • Entry in the lazarus.group DPRK IT-worker registry, which asserts that these accounts belong to one operator. The registry publishes no methodology, so this is recorded as its claim and not as a finding of this site. Its evidence links and its cross-references to other operators in the same registry are deliberately not reproduced as indicators.
    lazarus.group/team/ryuhei-matsuda — Lazarus Group DPRK IT-Worker Registry (lazarus.group) · under “Ryuhei Matsuda / ryuhei.eth / ryuheimat / ryuheimat3 / akame.eth / 0xhiros” · pulled 2026-09-09

0xd97729eef14c189144adb0591e4ddb1a66ce22af

wallet address IT Worker Fraud THIRD-PARTY REGISTRY

First seen unknown · last seen unknown

Source

  • Entry in the lazarus.group DPRK IT-worker registry, which asserts that these accounts belong to one operator. The registry publishes no methodology, so this is recorded as its claim and not as a finding of this site. Its evidence links and its cross-references to other operators in the same registry are deliberately not reproduced as indicators.
    lazarus.group/team/ryuhei-matsuda — Lazarus Group DPRK IT-Worker Registry (lazarus.group) · under “Ryuhei Matsuda / ryuhei.eth / ryuheimat / ryuheimat3 / akame.eth / 0xhiros” · pulled 2026-09-09

Sources

  • DPRK IT Workers — tayvano (lazarus-bluenoroff-research) · under “Ryuhei Matsuda” · published 2025-06-19 · pulled 2026-08-30
  • lazarus.group/team/ryuhei-matsuda — Lazarus Group DPRK IT-Worker Registry (lazarus.group) · under “Ryuhei Matsuda / ryuhei.eth / ryuheimat / ryuheimat3 / akame.eth / 0xhiros” · pulled 2026-09-09
  • github.com/jcking89 — Chollima Hunter · under “Ryuhei Matsuda” · published 2026-09-24 · pulled 2026-09-24
  • gitlab.com/ryuheimat — Chollima Hunter · under “Ryuhei Matsuda” · pulled 2026-09-13
  • keybase.io/ryuheimat — Chollima Hunter · under “Ryuhei Matsuda” · pulled 2026-09-17
  • hub.docker.com/u/ryuheimat — Chollima Hunter · under “Ryuhei Matsuda” · pulled 2026-09-17
  • gitlab.com/ryuheimat3 — Chollima Hunter · under “Ryuhei Matsuda” · pulled 2026-09-18

Back to all personas

Disclaimer An entry here is not proof of DPRK affiliation or wrongdoing. A listed name, account or address may belong to an uninvolved person, so each entry is a lead to verify independently. What inclusion means. Ryuhei Matsuda is the name an account presented under, not established to be the name of its operator.