reddy.kappeta@yandex.com

reddy.kappeta@yandex.com is an email address that 2 published sources report in connection with APT37 activity, which public reporting attributes to North Korea (DPRK). It is cited here from Genians. The reports are dated 2025-08-03.

email address APT37 MATCHED IN SOURCE

First seen 2025-08-03 · last seen 2025-08-03

Sources

  • Nearby text:

    …"email": "nusli.vakil@yandex.com" , "email_verified": true, "disabled": false, "country": "US", "locale": "en", "email": "reddy.kappeta@yandex.com" , "email_verified": true, "disabled": false, "country": "US", "locale": "en", "email": "leon24609@gmail.com" , "email_verified":…
    RoKRAT Shellcode and Steganographic Threats: Analysis and EDR Response Strategies — Genians · under “3-4. C2 Dropbox Account Information” · published 2025-08-03 · pulled 2026-09-11
  • Nearby text:

    …"email": "nusli.vakil@yandex.com" , "email_verified": true, "disabled": false, "country": "US", "locale": "en", "email": "reddy.kappeta@yandex.com" , "email_verified": true, "disabled": false, "country": "US", "locale": "en", "email": "leon24609@gmail.com" , "email_verified":…
    RoKRAT 셸코드 및 스테가노그래피 기반 위협 분석과 EDR 대응 방안 — Genians · under “3-4. C2 Dropbox 가입자 정보” · published 2025-08-03 · pulled 2026-09-12

Find this indicator in the index, or see every email address this site holds under Email addresses in the browse listing.

Related indicators

Cited by the same report: RoKRAT Shellcode and Steganographic Threats: Analysis and EDR Response Strategies

Genians lists 15 other indicators in this source. 7 are shown, chosen across types.

All 16 indicators from this source

Cited by the same report: RoKRAT 셸코드 및 스테가노그래피 기반 위협 분석과 EDR 대응 방안

Genians lists 9 other indicators in this source. 5 are shown, chosen across types.

All 10 indicators from this source

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. See the sourcing methodology.