Skip to content
Section B · Adversaries · Dossier
← Adversaries

File · Roaming Tiger · Unknown · misp-galaxy · refreshed 2026-10-06

Roaming Tiger

  • BRONZE WOODLAND
  • Rotten Tomato

sigil · no ATT&CK coverage stated

What changed

ledger · newest first
  1. —todaynew CVE2 new CVEs: CVE-2012-0158, CVE-2014-1761

CVEs cited sources tie to Roaming Tiger

none on KEV
  1. CVE-2014-17612026-10-17
    1. “Use of RTF vulnerabilities (CVE-2012-0158 and CVE-2014-1761)”

      cited as exploiting · named nearby · source: 2014.zeronights.org ↗ · 2026-10-17

  2. CVE-2012-01582026-10-17
    1. “As described in earlier reports on “Roaming Tiger”, the attack observed in August 2015 used weaponized exploit documents that leave Russian language decoy document files after infecting the system. The files exploit the well-known Microsoft Office vulnerability, CVE-2012-0158, to execute malicious code in order to take control of the targeted systems.”

      cited as used in a campaign · source: unit42.paloaltonetworks.com ↗ · 2026-10-17

    2. “Use of RTF vulnerabilities (CVE-2012-0158 and CVE-2014-1761)”

      cited as exploiting · named nearby · source: 2014.zeronights.org ↗ · 2026-10-17

Each line is what a source says, quoted, with the source linked under it. A citation is a source's claim, not our confirmation: read the source before you act on it.

Primary-source reports

via APTnotes · linked, never re-hosted
  1. 2015BBSRAT Attacks Targeting Russian Organizations Linked to Roaming TigerPalo Alto ↗
  2. 2014The Rotten Tomato CampaignSophos ↗
  3. 2014Roaming TigerESET ↗

Take it with you

keyless · no signup

References

3 sources
  1. 1.unit42.paloaltonetworks.com/bbsrat-attacks-targeting-russian-organizations-linked-…
  2. 2.2014.zeronights.org/assets/files/slides/roaming_tiger_zeronights_2014.pdf
  3. 3.secureworks.com/research/threat-profiles/bronze-woodland

Track Roaming Tiger on the wire.

This dossier is already data: the keyless actor API and a STIX 2.1 bundle. Mentions on the wire reach Telegram and RSS as they land.

Check your stack

Paste what you run: the CVEs exploited in the wild against it, and who is cited as exploiting them, with the report.

Stack checkNo key. No signup.